Table of Contents

Preface

Introduction to Cisco Firepower eXtensible Operating System Faults

FXOS Faults

FXOS Finite State Machine Faults

Troubleshooting Transient Faults

Introduction to System Event Log Messages

Baseboard Management Controller Messages

Cisco FXOS Faults and Error Messages, 2

Preface

This preface includes the following sections:

- Audience

- Organization

- Related Documentation

- Obtaining Documentation and Submitting a Service Request

Audience

This troubleshooting guide is designed for users who are responsible for troubleshooting issues that arise in the Cisco Firepower eXtensible Operating System.

Organization

This reference guide is organized into the following parts and chapters:

- Cisco Firepower eXtensible Operating System Faults

– Chapter 1, “Introduction to Cisco Firepower eXtensible Operating System Faults”

– Chapter 2, “FXOS Faults”

– Chapter 3, “FSM Faults”

– Chapter 4, “Troubleshooting Transient Faults”

- Cisco Firepower eXtensible Operating System SEL Messages

– Chapter 5, “Introduction to System Event Log Messages”

– Chapter 6, “Baseboard Management Controller Messages”

Related Documentation

A roadmap that lists all documentation for the Cisco Firepower eXtensible Operating System is available at the following URL:

http://www.cisco.com/go/firepower9300-docs

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.

Introduction to Cisco Firepower eXtensible Operating System Faults

This chapter provides an overview of Cisco Firepower eXtensible Operating System faults. This chapter contains the following sections:

- Overview of Faults

- Overview of the Finite State Machine

Overview of Faults

This section includes the following topics:

- About Faults in FXOS

- Fault Severities

- Fault Types

- Properties of Faults

- Lifecycle of Faults

- Fault Collection Policy

- Faults in Cisco Firepower eXtensible Operating System

About Faults in FXOS

A fault is a mutable object that is managed by the Cisco Firepower eXtensible Operating System. Each fault represents a failure or an alarm threshold that has been raised. During the lifecycle of a fault, it can change from one state or severity to another.

Each fault includes information about the operational state of the affected object at the time the fault was raised. If the fault is transitional and the failure is resolved, then the object transitions to a functional state.

A fault remains in FXOS until the fault is cleared and deleted according to the settings in the fault collection policy.

You can view all faults from either the FXOS CLI or the Firepower Chassis Manager. You can also configure the fault collection policy to determine how a FXOS instance collects and retains faults.

Note All Cisco Firepower eXtensible Operating System faults can be trapped by SNMP.

Fault Severities

Table 1-1 Fault Severities in FXOS

Severity

Description

Cleared

A notification that the condition that caused the fault has been resolved, and the fault has been cleared.

Condition

An informational message about a condition, possibly independently insignificant.

Critical

A service-affecting condition that requires immediate corrective action. For example, this severity could indicate that the managed object is out of service and its capability must be restored.

Info

A basic notification or informational message, possibly independently insignificant.

Major

A service-affecting condition that requires urgent corrective action. For example, this severity could indicate a severe degradation in the capability of the managed object and that its full capability must be restored.

Minor

A non-service-affecting fault condition that requires corrective action to prevent a more serious fault from occurring. For example, this severity could indicate that the detected alarm condition is not currently degrading the capacity of the managed object.

Warning

A potential or impending service-affecting fault that currently has no significant effects in the system. Action should be taken to further diagnose, if necessary, and correct the problem to prevent it from becoming a more serious service-affecting fault.

Fault Types

A fault can be one of the types described in Table 1-2.

Table 1-2 Types of Faults in FXOS

Type

Description

fsm

An FSM task has failed to complete successfully, or the FXOS is retrying one of the stages of the FSM.

equipment

FXOS has detected that a physical component is inoperable or has another functional issue.

server

FXOS is unable to complete a server task, such as associating a service profile with a server.

configuration

FXOS is unable to successfully configure a component.

environment

FXOS has detected a power problem, thermal problem, voltage problem, or a loss of CMOS settings.

management

FXOS has detected a serious management issue, such as one of the following:

- Critical services could not be started.

- The primary switch could not be identified.

- Components in the instance include incompatible firmware versions.

connectivity

FXOS has detected a connectivity problem, such as an unreachable adapter.

network

FXOS has detected a network issue, such as a link down.

operational

FXOS has detected an operational problem, such as a log capacity issue or a failed server discovery.

Properties of Faults

FXOS provides detailed information about each fault raised on the security appliance. Table 1-3 describes the fault properties that can be viewed in the FXOS CLI or the Firepower Chassis Manager.

Table 1-3 Fault Properties

Property Name

Description

Severity

The current severity level of the fault. This can be any of the severities described in Table 1-1.

Last Transition

The day and time on which the severity for the fault last changed. If the severity has not changed since the fault was raised, this property displays the original creation date.

Affected Object

The component that is affected by the condition that raised the fault.

Description

The description of the fault.

ID

The unique identifier assigned to the fault.

Status

Additional information about the fault state. This can be any of the states described in Table 1-4.

Type

The type of fault that has been raised. This can be any of the types described in Table 1-2.

Cause

The unique identifier associated with the condition that caused the fault.

Created at

The day and time when the fault occurred.

Code

The unique identifier assigned to the fault.

Number of Occurrences

The number of times the event that raised the fault occurred.

Original Severity

The severity assigned to the fault on the first time that it occurred.

Previous Severity

If the severity has changed, this is the previous severity.

Highest Severity

The highest severity encountered for this issue.

Lifecycle of Faults

FXOS faults are stateful, and a fault transitions through more than one state during its lifecycle. In addition, only one instance of a given fault can exist on each object. If the same fault occurs a second time, FXOS increases the number of occurrences by one.

A fault has the following lifecycle:

1. A condition occurs in the system and FXOS raises a fault in the active state.

2. If the fault is alleviated within a short period of time know as the flap interval, the fault severity remains at its original active value but the fault enters the soaking state. The soaking state indicates that the condition that raised the fault has cleared, but the system is waiting to see whether the fault condition reoccurs.

3. If the condition reoccurs during the flap interval, the fault enters the flapping state. Flapping occurs when a fault is raised and cleared several times in rapid succession. If the condition does not reoccur during the flap interval, the fault is cleared.

4. Once cleared, the fault enters the retention interval. This interval ensures that the fault reaches the attention of an administrator even if the condition that caused the fault has been alleviated, and that the fault is not deleted prematurely. The retention interval retains the cleared fault for the length of time specified in the fault collection policy.

5. If the condition reoccurs during the retention interval, the fault returns to the active state. If the condition does not reoccur, the fault is deleted.

Table 1-4 Fault Lifecycle States

State

Description

Soaking

A fault was raised and then cleared within a short time known as the flap interval. Since this may be a flapping condition, the fault severity remains at its original active value, but this state indicates that the condition that raised the fault has cleared.

If the fault does not reoccur, the fault moves into the cleared state. Otherwise, the fault moves into the flapping state.

Flapping

A fault was raised, cleared, and then raised again within a short time known as the flap interval.

Fault Collection Policy

The fault collection policy controls the lifecycle of a fault, including the length of time that each fault remains in the flapping and retention intervals.

Faults in Cisco Firepower eXtensible Operating System

This section includes the following topics:

- Faults in Firepower Chassis Manager

- Faults in FXOS CLI

Faults in Firepower Chassis Manager

To view the faults for all objects in the system, navigate to the Overview page in the Firepower Chassis Manager. Each fault severity is represented by a different icon. Above the fault listing you can see how many critical and major faults have occurred in the system. When you double-click a specific fault, Firepower Chassis Manager opens the Faults Properties dialog box and displays details for that fault.

Faults in FXOS CLI

If you want to view the faults for all objects in the system, at the top-level scope, enter the show fault command. If you want to view faults for a specific object, scope to that object and then enter the show fault command.

If you want to view all of the available details about a fault, enter the show fault detail command.

Overview of the Finite State Machine

This section includes the following topics:

- About the Finite State Machine in Cisco Firepower eXtensible Operating System

- FSM Stage Names

- FSM in Cisco Firepower eXtensible Operating System

About the Finite State Machine in Cisco Firepower eXtensible Operating System

A finite state machine (FSM) is a workflow model, similar to a flow chart, that is composed of the following:

- Finite number of stages (states)

- Transitions between those stages

- Operations

The current stage in the FSM is determined by past stages and the operations performed to transition between the stages. A transition from one stage to another stage is dependent on the success or failure of an operation.

FXOS uses FSM tasks that run in the Data Management Engine (DME) to manage end points in the Firepower object model, including the following:

- Physical components (chassis, I/O module, servers)

- Logical components (LAN cloud, policies)

- Workflows (server discovery, service profile management, downloads, upgrades, backups)

The DME manages the FSM stages and transition, and instructs the Application Gateway (AG) to perform operations on the managed end points. Therefore, each stage can be considered to be an interaction between the DME, the AG, and the managed end point. The AGs do the real work of interacting with managed end points.

When all of the FSM stages have run successfully, the FXOS considers that the FSM operation is successful.

If the FSM encounters an error or a timeout at a stage, the FSM retries that stage at scheduled intervals. When the retry count has been reached for that stage, the FSM stops and the FXOS declares that the change has failed. If an FSM task fails, the FXOS raises the appropriate faults and alarms.

Multiple FSM tasks can be associated to an end point. However, only one FSM task at a time can run. Additional FSM tasks for the same end point are placed in a queue and are scheduled to be run when the previous FSM task is either successfully completed or the task fails.

You can view the FSM details for a particular end point to determine if a task succeeded or failed. You can also use the FSM to troubleshoot any failures.

FSM Stage Names

The FSM stage names are constructed using the following notation

FsmObjectWorkflowOperationWhere-is-it-executed

where:

- Object is the object that the FSM is running, such as the Blade or Chassis.

- Workflow is the overall task being performed by the FSM, such as Discover or Association.

- Operation is the task being performed at a particular stage, such as Pnuos-Config.

- Where-is-it-executed is generally “”, or “A” or “B” or “Local” or “Peer”. If this is not specified, it is executed on the managingInst node.

Each FSM stage name has a prefix that identifies the FSM and a suffix that identifies a stage within the FSM. The prefix notation is FsmObjectWorkflow and the suffix notation is OperationWhere-is-it-executed. For example, if the FSM name is FsmComputeBladeDiscoverBmcInventory:

- The prefix is FsmComputeBladeDiscover

- The suffix is BmcInventory

FSM in Cisco Firepower eXtensible Operating System

The FXOS CLI can display the FSM information for an end point when you are in the command mode for that end point.

Enter the show fsm status command in the appropriate mode to view the current FSM task for an end point. The information displayed about a current FSM task in the CLI is static. You must re-enter the command to see the progress updates. The following example displays the information about the current FSM task for the server in chassis 1, slot 6:

Firepower# scope server 1/1

Firepower /chassis/server # show fsm status

Slot: 1

Server: sys/chassis-1/blade-1

FSM 1:

Remote Result: Not Applicable

Remote Error Code: None

Remote Error Description:

Status: Discover Blade Boot Wait

Previous Status: Discover Blade Boot Wait

Timestamp: 2006-01-26T23:31:36

Try: 0

Flags: 0

Progress (%): 33

Current Task: Waiting for system reset on server 1/1 (FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootWait)

Enter the show fsm task command in the appropriate mode to view all of the pending tasks in the FSM queue. The following example displays the FSM task queue for chassis 1, slot 1:

Firepower# scope server 1/1

Firepower /chassis/server # show fsm task

FSM Task:

Item ID Completion FSM Flags

---------------- -------- ------------ ---------

Powercycle 1154858 Scheduled

BiosRecovery 1154860 Scheduled

FXOS Faults

This chapter provides information about the faults that may be raised in FXOS.

fltFabricComputeSlotEpMisplacedInChassisSlot

Fault Code: F0156

Message

Server, vendor([vendor]), model([model]), serial([serial]) in slot [chassisId]/[slotId] presence: [presence]

Explanation

This fault typically occurs when Cisco FPR Manager detects a server in a chassis slot that does not match what was previously equipped in the slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the previous server was intentionally removed and a new one was inserted, reacknowledge the server.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: server-moved

mibFaultCode: 156

mibFaultName: fltFabricComputeSlotEpMisplacedInChassisSlot

moClass: fabric:ComputeSlotEp

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fltFabricComputeSlotEpServerIdentificationProblem

Fault Code: F0157

Message

Problem identifying server in slot [chassisId]/[slotId]

Explanation

This fault typically occurs when Cisco FPR Manager encountered a problem identifying the server in a chassis slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reinsert the server.

Step 2 Reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: server-identification-problem

mibFaultCode: 157

mibFaultName: fltFabricComputeSlotEpServerIdentificationProblem

moClass: fabric:ComputeSlotEp

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fltVnicEtherConfig-failed

Fault Code: F0169

Message

Eth vNIC [name], service profile [name] failed to apply configuration

Explanation

This fault typically occurs when Cisco FPR Manager could not place the vNIC on the vCon.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server was successfully discovered.

Step 2 Verify that the correct type of adapters are installed on the server.

Step 3 Confirm that the vCon assignment is correct.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: configuration-failed

mibFaultCode: 169

mibFaultName: fltVnicEtherConfigFailed

moClass: vnic:Ether

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltProcessorUnitInoperable

Fault Code: F0174

Message

Processor [id] on server [chassisId]/[slotId] operability: [operability]

Explanation

This fault occurs in the unlikely event that processor is inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 174

mibFaultName: fltProcessorUnitInoperable

moClass: processor:Unit

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitThermalNonCritical

Fault Code: F0175

Message

Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the processor temperature on a blade or rack server exceeds a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: thermal-problem

mibFaultCode: 175

mibFaultName: fltProcessorUnitThermalNonCritical

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitThermalThresholdCritical

Fault Code: F0176

Message

Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the processor temperature on a blade or rack server exceeds a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 176

mibFaultName: fltProcessorUnitThermalThresholdCritical

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitThermalThresholdNonRecoverable

Fault Code: F0177

Message

Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the processor temperature on a blade or rack server has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 177

mibFaultName: fltProcessorUnitThermalThresholdNonRecoverable

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitVoltageThresholdNonCritical

Fault Code: F0178

Message

Processor [id] on server [chassisId]/[slotId] voltage: [voltage]Processor [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the processor voltage is out of normal operating range, but hasn’t yet reached a critical stage. Normally the processor recovers itself from this situation

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the processor for further degradation.

Step 2 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 3 In Cisco FPR Manager, decommission and then recommission the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: voltage-problem

mibFaultCode: 178

mibFaultName: fltProcessorUnitVoltageThresholdNonCritical

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitVoltageThresholdCritical

Fault Code: F0179

Message

Processor [id] on server [chassisId]/[slotId] voltage: [voltage]Processor [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the processor voltage has exceeded the specified hardware voltage rating.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 179

mibFaultName: fltProcessorUnitVoltageThresholdCritical

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltProcessorUnitVoltageThresholdNonRecoverable

Fault Code: F0180

Message

Processor [id] on server [chassisId]/[slotId] voltage: [voltage]Processor [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the processor voltage has exceeded the specified hardware voltage rating and may cause processor hardware damage or jeopardy.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: voltage-problem

mibFaultCode: 180

mibFaultName: fltProcessorUnitVoltageThresholdNonRecoverable

moClass: processor:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltStorageLocalDiskInoperable

Fault Code: F0181

Message

Local disk [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Local disk [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the local disk has become inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Insert the disk in a supported slot.

Step 2 Remove and reinsert the local disk.

Step 3 Replace the disk, if an additional disk is available.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 181

mibFaultName: fltStorageLocalDiskInoperable

moClass: storage:LocalDisk

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageItemCapacityExceeded

Fault Code: F0182

Message

Disk usage for partition [name] on fabric interconnect [id] exceeded 70%

Explanation

This fault occurs when the partition disk usage exceeds 70% but is less than 90%.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reduce the partition disk usage to less than 70% by deleting unused and unnecessary files.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: capacity-exceeded

mibFaultCode: 182

mibFaultName: fltStorageItemCapacityExceeded

moClass: storage:Item

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/stor-part-[name]

fltStorageItemCapacityWarning

Fault Code: F0183

Message

Disk usage for partition [name] on fabric interconnect [id] exceeded 90%

Explanation

This fault occurs when the partition disk usage exceeds 90%.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reduce the partition disk usage to less than 90% by deleting unused and unnecessary files.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: capacity-exceeded

mibFaultCode: 183

mibFaultName: fltStorageItemCapacityWarning

moClass: storage:Item

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/stor-part-[name]

fltMemoryUnitDegraded

Fault Code: F0184

Message

DIMM [location] on server [chassisId]/[slotId] operability: [operability]DIMM [location] on server [id] operability: [operability]

Explanation

This fault occurs when a DIMM is in a degraded operability state. This state typically occurs when an excessive number of correctable ECC errors are reported on the DIMM by the server BIOS.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the error statistics on the degraded DIMM through Cisco FPR Manager. If the high number of errors persists, there is a high possibility of the DIMM becoming inoperable.

Step 2 If the DIMM becomes inoperable, replace the DIMM.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 184

mibFaultName: fltMemoryUnitDegraded

moClass: memory:Unit

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltMemoryUnitInoperable

Fault Code: F0185

Message

DIMM [location] on server [chassisId]/[slotId] operability: [operability]DIMM [location] on server [id] operability: [operability]

Explanation

This fault typically occurs because an above threshold number of correctable or uncorrectable errors has occurred on a DIMM. The DIMM may be inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, review the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 If necessary, replace the DIMM.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 185

mibFaultName: fltMemoryUnitInoperable

moClass: memory:Unit

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltMemoryUnitThermalThresholdNonCritical

Fault Code: F0186

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server exceeds a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: thermal-problem

mibFaultCode: 186

mibFaultName: fltMemoryUnitThermalThresholdNonCritical

moClass: memory:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltMemoryUnitThermalThresholdCritical

Fault Code: F0187

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server exceeds a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 187

mibFaultName: fltMemoryUnitThermalThresholdCritical

moClass: memory:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltMemoryUnitThermalThresholdNonRecoverable

Fault Code: F0188

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server has been out of the operating range, and the issue is not recoverable.Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 188

mibFaultName: fltMemoryUnitThermalThresholdNonRecoverable

moClass: memory:Unit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltMemoryArrayVoltageThresholdNonCritical

Fault Code: F0189

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage is out of normal operating range, but hasn’t yet reached a critical stage. Typically the memory array recovers itself from this situation.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, look at the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the blade and re-insert into the chassis.

Step 4 In Cisco FPR Manager, decommission and recommission the server.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: voltage-problem

mibFaultCode: 189

mibFaultName: fltMemoryArrayVoltageThresholdNonCritical

moClass: memory:Array

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]

fltMemoryArrayVoltageThresholdCritical

Fault Code: F0190

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage exceeds the specified hardware voltage rating

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, look at the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the blade and re-insert into the chassis.

Step 4 In Cisco FPR Manager, decommission and recommission the server.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 190

mibFaultName: fltMemoryArrayVoltageThresholdCritical

moClass: memory:Array

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]

fltMemoryArrayVoltageThresholdNonRecoverable

Fault Code: F0191

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage exceeded the specified hardware voltage rating and potentially memory hardware may be in damage or jeopardy

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, review the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the server from the chassis and re-insert it.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: voltage-problem

mibFaultCode: 191

mibFaultName: fltMemoryArrayVoltageThresholdNonRecoverable

moClass: memory:Array

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]

fltAdaptorUnitUnidentifiable-fru

Fault Code: F0200

Message

Adapter [id] in server [id] has unidentified FRUAdapter [id] in server [chassisId]/[slotId] has unidentified FRU

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported adapter. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter is installed.

Step 2 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: unidentifiable-fru

mibFaultCode: 200

mibFaultName: fltAdaptorUnitUnidentifiableFru

moClass: adaptor:Unit

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]

fltAdaptorUnitMissing

Fault Code: F0203

Message

Adapter [id] in server [id] presence: [presence]Adapter [id] in server [chassisId]/[slotId] presence: [presence]

Explanation

The adaptor is missing. Cisco FPR Manager raises this fault when any of the following scenarios occur:

- The endpoint reports there is no adapter in the adaptor slot.

- The endpoint cannot detect or communicate with the adapter in the adaptor slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure an adapter is inserted in the adaptor slot in the server.

Step 2 Check whether the adaptor is connected and configured properly and is running the recommended firmware version.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-missing

mibFaultCode: 203

mibFaultName: fltAdaptorUnitMissing

moClass: adaptor:Unit

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]

fltAdaptorUnitAdaptorReachability

Fault Code: F0206

Message

Adapter [id]/[id] is unreachableAdapter [chassisId]/[slotId]/[id] is unreachable

Explanation

Cisco FPR Manager cannot access the adapter. This fault typically occurs as a result of one of the following issues:

- The server does not have sufficient power.

- The I/O module is not functional.

- The adapter firmware has failed.

- The adapter is not functional

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 In Cisco FPR Manager, check the power state of the server.

Step 3 Verify that the physical server has the same power state.

Step 4 If the server is off, turn the server on.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: connectivity-problem

mibFaultCode: 206

mibFaultName: fltAdaptorUnitAdaptorReachability

moClass: adaptor:Unit

Type: connectivity

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]

fltAdaptorHostIfLink-down

Fault Code: F0207

Message

Adapter [transport] host interface [id]/[id]/[id] link state: [linkState]Adapter [transport] host interface [chassisId]/[slotId]/[id]/[id] link state: [linkState]

Explanation

This fault typically occurs as a result of one of the following issues:

- The fabric interconnect is in End-Host mode, and all uplink ports failed.

- The server port to which the adapter is pinned failed.

- A transient error caused the link to fail.

Recommended Action

If you see this fault, take the following actions:

Step 1 If an associated port is disabled, enable the port.

Step 2 Reacknowledge the server with the adapter that has the failed link.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: link-down

mibFaultCode: 207

mibFaultName: fltAdaptorHostIfLinkDown

moClass: adaptor:HostIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-iscsi-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-service-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-iscsi-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-service-eth-[id]

fltAdaptorExtIfLink-down

Fault Code: F0209

Message

Adapter uplink interface [id]/[id]/[id] link state: [linkState]. Please verify connectivity to Fabric Interconnect. Acknowledging FEX might be required.Adapter uplink interface [chassisId]/[slotId]/[id]/[id] on security module [slotId] link state: [linkState]. Please check switch blade-facing port status. Resetting security module might be required.

Explanation

The link for a network facing adapter interface is down. Cisco FPR Manager raises this fault when any of the following scenarios occur:

- Cisco FPR Manager cannot establish and/or validate the adapter’s connectivity to any of the fabric interconnects.

- The endpoint reports a link down or vNIC down event on the adapter link.

- The endpoint reports an errored link state or errored vNIC state event on the adapter link.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the adapter is connected, configured properly, and is running the recommended firmware version.

Step 2 If the server is stuck at discovery, decommission the server and reacknowledge the server slot.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: link-down

mibFaultCode: 209

mibFaultName: fltAdaptorExtIfLinkDown

moClass: adaptor:ExtIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fltPortPIoLink-down

Fault Code: F0276

Message

[transport] port [portId] on chassis [id] oper state: [operState], reason: [stateQual][transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual][transport] port [slotId]/[portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

Explanation

This fault occurs when a fabric interconnect port is in link-down state. This state impacts the traffic destined for the port.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the physical link is properly connected between the fabric interconnect and the peer component.

Step 2 Verify that the configuration on the peer entity is properly configured and matches the fabric interconnect port configuration.

Step 3 Unconfigure and re-configure the port.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: link-down

mibFaultCode: 276

mibFaultName: fltPortPIoLinkDown

moClass: port:PIo

Type: network

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltPortPIoFailed

Fault Code: F0277

Message

[transport] port [portId] on chassis [id] oper state: [operState], reason: [stateQual][transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual][transport] port [slotId]/[portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

Explanation

This fault is raised on fabric interconnect ports and on server-facing ports on an IOM or a FEX module when FPRM detects that the port is not up and in failed state while it is expected to be up since it has been enabled by user and there is no known hardware failure or missing SFP issue and port license is valid. Additional reason is displayed by the fault description string.

Recommended Action

If you see this fault, Corrective action maybe taken based on reason information in the fault description whenever such a reason is displayed. If the fault description displays reason as "ENM source pinning failed" then it means that the fabric interconnect is operating in End-host Node Mode and the uplink port that this server facing port is pinned to is down or does not have appropriate VLAN configured. In case of such an error for an appliance port check the VLAN configuration on uplink port. A VLAN with same id as the one on the appliance port will also need to be configured on the uplink port. After setting the configuration right if you still see the fault then create a show tech-support file for Cisco FPR Manager and the chassis or FEX module, and then contact Cisco TAC.

Fault Details

Severity: major

Cause: port-failed

mibFaultCode: 277

mibFaultName: fltPortPIoFailed

moClass: port:PIo

Type: network

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltPortPIoHardware-failure

Fault Code: F0278

Message

[transport] port [portId] on chassis [id] oper state: [operState], reason: hardware-failure[transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] oper state: [operState], reason: hardware-failure[transport] port [slotId]/[portId] on fabric interconnect [id] oper state: [operState], reason: hardware-failure

Explanation

This fault is raised on fabric interconnect ports and server-facing ports on an IOM or a FEX module when the system detects a hardware failure.

Recommended Action

If you see this fault, create a show tech-support file for Cisco FPR Manager and the chassis or FEX module, and then contact Cisco TAC.

Fault Details

Severity: major

Cause: port-failed

mibFaultCode: 278

mibFaultName: fltPortPIoHardwareFailure

moClass: port:PIo

Type: network

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltPortPIoSfp-not-present

Fault Code: F0279

Message

[transport] port [portId] on chassis [id] oper state: [operState][transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] oper state: [operState][transport] port [slotId]/[portId] on fabric interconnect [id] oper state: [operState]

Explanation

When a fabric interconnect port is not in an unconfigured state, an SFP is required for its operation. This fault is raised to indicate that the SFP is missing from a configured port.

Recommended Action

If you see this fault, insert a supported SFP into the port on the fabric interconnect. A list of supported SFPs can be found on www.Cisco.com.

Fault Details

Severity: info

Cause: port-failed

mibFaultCode: 279

mibFaultName: fltPortPIoSfpNotPresent

moClass: port:PIo

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltFabricExternalPcDown

Fault Code: F0282

Message

[type] port-channel [portId] on fabric interconnect [switchId] oper state: [operState], reason: [stateQual][type] port-channel [portId] on fabric interconnect [switchId] oper state: [operState], reason: [stateQual]

Explanation

This fault typically occurs when a fabric interconnect reports that a fabric port channel is operationally down.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the member ports in the fabric port channel are administratively up and operational. Check the link connectivity for each port.

Step 2 If connectivity seems correct, check the operational states on the peer switch ports of the port channel members.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: operational-state-down

mibFaultCode: 282

mibFaultName: fltFabricExternalPcDown

moClass: fabric:ExternalPc

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]

Affected MO: fabric/eth-estc/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/fc-estc/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]

Affected MO: fabric/fc-estc/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/lan/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/lan/[id]/net-group-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]

Affected MO: fabric/lan/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/lan/net-group-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]

Affected MO: fabric/san/[id]/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]

Affected MO: fabric/san/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]

Affected MO: fabric/san/[id]/pc-[portId]

Affected MO: fabric/san/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]

Affected MO: fabric/san/net-[name]/pc-switch-[switchId]-pc-[portId]

fltDcxVcDown

Fault Code: F0283

Message

[transport] VIF [id] on server [chassisId] / [slotId] of switch [switchId] down, reason: [stateQual][transport] VIF [id] on server [id] of switch [switchId] down, reason: [stateQual]

Explanation

This fault typically occurs when a fabric interconnect reports one of the following connectivity states for a virtual interface:

- Down

- Errored

- Unavailable

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the uplink physical interface is up.

Step 2 If the vNIC/vHBA is configured for a pin group, verify that the pin group targets are configured correctly.

Step 3 In the Network Control Policy for the vNIC, verify that the ’Action on Uplink Fail’ field is set to ’warning’.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: link-down

mibFaultCode: 283

mibFaultName: fltDcxVcDown

moClass: dcx:Vc

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/switch-[id]/ethlanflowmon/vc-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vc-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]/vc-[id]

fltNetworkElementInoperable

Fault Code: F0291

Message

Fabric Interconnect [id] operability: [operability]

Explanation

This fault typically occurs when the fabric interconnect cluster controller reports that the membership state of the fabric interconnect is down, indicating that the fabric interconnect is inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both fabric interconnects in the cluster are running the same Kernel and System software versions.

Step 2 Verify that the fabric interconnects software version and the Cisco FPR Manager software versions are the same.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 291

mibFaultName: fltNetworkElementInoperable

moClass: network:Element

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]

fltMgmtEntityDegraded

Fault Code: F0293

Message

Fabric Interconnect [id], HA Cluster interconnect link failure

Explanation

This fault occurs when one of the cluster links (either L1 or L2) of a fabric interconnect is not operationally up. This issue impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both L1 and L2 links are properly connected between the fabric interconnects.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: link-down

mibFaultCode: 293

mibFaultName: fltMgmtEntityDegraded

moClass: mgmt:Entity

Type: network

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityDown

Fault Code: F0294

Message

Fabric Interconnect [id], HA Cluster interconnect total link failure

Explanation

This fault occurs when both cluster links (L1 and L2) of the fabric interconnects are in a link-down state. This issue impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both L1 and L2 links are properly connected between the fabric interconnects.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: link-down

mibFaultCode: 294

mibFaultName: fltMgmtEntityDown

moClass: mgmt:Entity

Type: network

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltDcxNsFailed

Fault Code: F0304

Message

Server [chassisId]/[slotId] (service profile: [assignedToDn]) virtual network interface allocation failed.Server [id] (service profile: [assignedToDn]) virtual network interface allocation failed.

Explanation

The adapter’s vif-namespace activation failed due to insufficient resources. Cisco FPR Manager raises this fault when the number of deployed VIF resources exceeds the maximum VIF resources available on the adapter connected to the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the NS "size" and "used" resources to determine by how many vNICs the adapter exceeded the maximum.

Step 2 Unconfigure or delete all vNICs on the adapter above the maximum number.

Step 3 Add additional fabric uplinks from the IOM to the corresponding fabric interconnect and reacknowledge the chassis. This increases the "NS size" on the adapter.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: insufficient-resources

mibFaultCode: 304

mibFaultName: fltDcxNsFailed

moClass: dcx:Ns

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/dcxns-[switchId]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/dcxns-[switchId]

fltComputePhysicalInsufficientlyEquipped

Fault Code: F0305

Message

Server [id] (service profile: [assignedToDn]) has insufficient number of DIMMs, CPUs and/or adaptersServer [chassisId]/[slotId] (service profile: [assignedToDn]) has insufficient number of DIMMs, CPUs and/or adapters

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the server has an insufficient number of DIMMs, CPUs, and/or adapters.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the DIMMs are installed in a supported configuration.

Step 2 Verify that an adapter and CPU are installed.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: insufficiently-equipped

mibFaultCode: 305

mibFaultName: fltComputePhysicalInsufficientlyEquipped

moClass: compute:Physical

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalIdentityUnestablishable

Fault Code: F0306

Message

Server [id] (service profile: [assignedToDn]) has an invalid FRUServer [chassisId]/[slotId] (service profile: [assignedToDn]) has an invalid FRU

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported server or CPU.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported server and/or CPU is installed.

Step 2 Verify that the Cisco FPR Manager capability catalog is up to date.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: identity-unestablishable

mibFaultCode: 306

mibFaultName: fltComputePhysicalIdentityUnestablishable

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputeBoardPowerError

Fault Code: F0310

Message

Motherboard of server [chassisId]/[slotId] (service profile: [assignedToDn]) power: [operPower]Motherboard of server [id] (service profile: [assignedToDn]) power: [operPower]

Explanation

This fault typically occurs when the server power sensors have detected a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure that the server is correctly installed in the chassis and that all cables are secure.

Step 2 If you reinstalled the server, reacknowledge it.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-problem

mibFaultCode: 310

mibFaultName: fltComputeBoardPowerError

moClass: compute:Board

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/rack-unit-[id]/board

fltComputePhysicalPowerProblem

Fault Code: F0311

Message

Server [id] (service profile: [assignedToDn]) oper state: [operState]Server [chassisId]/[slotId] (service profile: [assignedToDn]) oper state: [operState]

Explanation

This fault typically occurs when the server power sensors have detected a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure that the server is correctly installed in the chassis and that all cables are secure.

Step 2 If you reinstalled the server, reacknowledge it.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-problem

mibFaultCode: 311

mibFaultName: fltComputePhysicalPowerProblem

moClass: compute:Physical

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalThermalProblem

Fault Code: F0312

Message

Server [id] (service profile: [assignedToDn]) oper state: [operState]Server [chassisId]/[slotId] (service profile: [assignedToDn]) oper state: [operState]

Explanation

This fault typically occurs when the server thermal sensors have detected a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure that the server fans are working properly.

Step 2 Wait for 24 hours to see if the problem resolves itself.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 312

mibFaultName: fltComputePhysicalThermalProblem

moClass: compute:Physical

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalBiosPostTimeout

Fault Code: F0313

Message

Server [id] (service profile: [assignedToDn]) BIOS failed power-on self testServer [chassisId]/[slotId] (service profile: [assignedToDn]) BIOS failed power-on self test

Explanation

This fault typically occurs when the server has encountered a diagnostic failure.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 Reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 313

mibFaultName: fltComputePhysicalBiosPostTimeout

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalDiscoveryFailed

Fault Code: F0314

Message

Server [id] (service profile: [assignedToDn]) discovery: [discovery]Server [chassisId]/[slotId] (service profile: [assignedToDn]) discovery: [discovery]

Explanation

This fault typically occurs for one of the following reasons:

- The shallow discovery that occurs when the server associated with service profile failed.

- The server is down.

- The data path is not working.

- Cisco FPR Manager cannot communicate with the CIMC on the server.

- The server cannot communicate with the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FSM tab and the current state of the server and any FSM operations.

Step 2 Check the error descriptions and see if any server components indicate a failure.

Step 3 If the server or a server component has failed, do the following:

a. Check the operational state of the server.

b. If the server is not operable, re-acknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: discovery-failed

mibFaultCode: 314

mibFaultName: fltComputePhysicalDiscoveryFailed

moClass: compute:Physical

Type: operational

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalAssociationFailed

Fault Code: F0315

Message

Service profile [assignedToDn] failed to associate with server [id]Service profile [assignedToDn] failed to associate with server [chassisId]/[slotId]

Explanation

This fault typically occurs for one of the following reasons:

- The service profile could not be associated with the server.

- The server is down.

- The data path is not working.

- Cisco FPR Manager cannot communicate with one or more of the fabric interconnect, the server, or a component on the server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FSM tab and the current state of the server and any FSM operations.

Step 2 If the server is stuck in an inappropriate state, such as booting, power cycle the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: association-failed

mibFaultCode: 315

mibFaultName: fltComputePhysicalAssociationFailed

moClass: compute:Physical

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalInoperable

Fault Code: F0317

Message

Server [id] (service profile: [assignedToDn]) health: [operability]Server [chassisId]/[slotId] (service profile: [assignedToDn]) health: [operability]

Explanation

This fault typically occurs when the server has encountered a diagnostic failure.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server.In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 Reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 317

mibFaultName: fltComputePhysicalInoperable

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalUnassignedMissing

Fault Code: F0318

Message

Server [id] (no profile) missingServer [chassisId]/[slotId] (no profile) missing

Explanation

This fault typically occurs when the server, which is not associated with a service profile, was previously physically inserted in the slot, but cannot be detected by Cisco FPR Manager.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the server is physically present in the slot, remove and then reinsert it.

Step 2 If the server is not physically present in the slot, insert it.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-missing

mibFaultCode: 318

mibFaultName: fltComputePhysicalUnassignedMissing

moClass: compute:Physical

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalAssignedMissing

Fault Code: F0319

Message

Server [id] (service profile: [assignedToDn]) missingServer [chassisId]/[slotId] (service profile: [assignedToDn]) missing

Explanation

This fault typically occurs when the server, which is associated with a service profile, was previously physically inserted in the slot, but cannot be detected by Cisco FPR Manager.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the server is physically present in the slot, remove and then reinsert it.

Step 2 If the server is not physically present in the slot, reinsert it.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-missing

mibFaultCode: 319

mibFaultName: fltComputePhysicalAssignedMissing

moClass: compute:Physical

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalUnidentified

Fault Code: F0320

Message

Server [id] (service profile: [assignedToDn]) has an invalid FRU: [presence]Server [chassisId]/[slotId] (service profile: [assignedToDn]) has an invalid FRU: [presence]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported server or CPU.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported server and/or CPU is installed.

Step 2 Verify that the Cisco FPR Manager capability catalog is up to date.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: identity-unestablishable

mibFaultCode: 320

mibFaultName: fltComputePhysicalUnidentified

moClass: compute:Physical

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalUnassignedInaccessible

Fault Code: F0321

Message

Server [id] (no profile) inaccessibleServer [chassisId]/[slotId] (no profile) inaccessible

Explanation

This fault typically occurs when the server, which is not associated with a service profile, has lost connection to the fabric interconnects. This fault occurs if there are communication issues between the server CIMC and the fabric interconnects.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the fault does not clear after a brief time, remove the server and then reinsert it.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-inaccessible

mibFaultCode: 321

mibFaultName: fltComputePhysicalUnassignedInaccessible

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalAssignedInaccessible

Fault Code: F0322

Message

Server [id] (service profile: [assignedToDn]) inaccessibleServer [chassisId]/[slotId] (service profile: [assignedToDn]) inaccessible

Explanation

This fault typically occurs when the server, which is associated with a service profile, has lost connection to the fabric interconnects. This fault occurs if there are communication issues between the server CIMC and the fabric interconnects.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the fault does not clear after a brief time, remove the server and then reinsert it.

Step 3 Reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-inaccessible

mibFaultCode: 322

mibFaultName: fltComputePhysicalAssignedInaccessible

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltLsServerFailed

Fault Code: F0324

Message

Service profile [name] failed

Explanation

Server has failed. This fault typically occurs if the adapter power on self-test results in major and critical errors.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: server-failed

mibFaultCode: 324

mibFaultName: fltLsServerFailed

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerDiscoveryFailed

Fault Code: F0326

Message

Service profile [name] discovery failed

Explanation

The shallow discovery that occurs when the server associated with service profile fails. If the server is up and the data path is working, this fault typically occurs as a result of one of the following issues:

- Cisco FPR Manager cannot communicate with the CIMC on the server.

- The server cannot communicate with the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FSM tab and view the current state of the server and any FSM operations.

Step 2 Check the error descriptions and see if any server components indicate a failure.

Step 3 If the server or a server component has failed, do the following:

a. Check the operational state of the server.

b. If the server is not operable, reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: discovery-failed

mibFaultCode: 326

mibFaultName: fltLsServerDiscoveryFailed

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerConfigFailure

Fault Code: F0327

Message

Service profile [name] configuration failed due to [configQualifier]

Explanation

The named configuration qualifier is not available. This fault typically occurs because Cisco FPR Manager cannot successfully deploy the service profile due to a lack of resources that meet the named qualifier. For example, this fault can occur if the following occurs:

- The service profile is configured for a server adapter with vHBAs, and the adapter on the server does not support vHBAs.

- The service profile is created from a template which includes a server pool, and the server pool is empty.

- The local disk configuration policy in the service profile specifies the No Local Storage mode, but the server contains local disks.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.

Step 2 Check the state of the server and ensure that it is in either the discovered or unassociated state.

Step 3 If the server is associated or undiscovered, do one of the following:

– Discover the server.

– Disassociate the server from the current service profile.

– Select another server to associate with the service profile.

Step 4 Review each policy in the service profile and verify that the selected server meets the requirements in the policy.

Step 5 If the server does not meet the requirements of the service profile, do one of the following:

– Modify the service profile to match the server.

– Select another server that does meet the requirements to associate with the service profile.

Step 6 If you can verify that the server meets the requirements of the service profile, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: configuration-failure

mibFaultCode: 327

mibFaultName: fltLsServerConfigFailure

moClass: ls:Server

Type: server

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerMaintenanceFailed

Fault Code: F0329

Message

Service profile [name] maintenance failed

Explanation

Cisco FPR Manager currently does not use this fault.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: maintenance-failed

mibFaultCode: 329

mibFaultName: fltLsServerMaintenanceFailed

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerRemoved

Fault Code: F0330

Message

Service profile [name] underlying resource removed

Explanation

Cisco FPR Manager cannot access the server associated with the service profile. This fault typically occurs as a result of one of the following issues:

- The server has been physically removed from the slot.

- The server is not available.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the server was removed from the slot, reinsert the server in the slot.

Step 2 If the server was not removed, remove and reinsert the server.NOTE: If the server is operable, this action can be disruptive to current operations.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-removed

mibFaultCode: 330

mibFaultName: fltLsServerRemoved

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerInaccessible

Fault Code: F0331

Message

Service profile [name] cannot be accessed

Explanation

Cisco FPR Manager cannot communicate with the CIMC on the server. This fault typically occurs as a result of one of the following issues:

- The server port or ports have failed.

- The I/O module is offline.

- The BMC has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 If Cisco FPR Manager shows that the CIMC is down, physically reseat the server.

Step 2 If Cisco FPR Manager shows that the server ports have failed, attempt to enable them.

Step 3 If the I/O module is offline, check for faults on that component.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: server-inaccessible

mibFaultCode: 331

mibFaultName: fltLsServerInaccessible

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerAssociationFailed

Fault Code: F0332

Message

Service profile [name] association failed for [pnDn]

Explanation

The service profile could not be associated with the server. This fault typically occurs because Cisco FPR Manager cannot communicate with one or more of the following:

- Fabric interconnect

- CIMC on the server

- SAS controller driver

- Server

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FSM tab for the server and service profile to determine why the association failed.

Step 2 If the server is stuck in an inappropriate state, such as booting, power cycle the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: association-failed

mibFaultCode: 332

mibFaultName: fltLsServerAssociationFailed

moClass: ls:Server

Type: server

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerUnassociated

Fault Code: F0334

Message

Service profile [name] is not associated

Explanation

The service profile has not yet been associated with a server or a server pool. This fault typically occurs as a result of one of the following issues:

- There is no acceptable server in the server pool.

- The association failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 If you did not intend to associate the service profile, ignore the fault.

Step 2 If you did intend to associate the service profile, check the association failure fault.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: unassociated

mibFaultCode: 334

mibFaultName: fltLsServerUnassociated

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsServerServer-unfulfilled

Fault Code: F0337

Message

Server [pnDn] does not fulfill Service profile [name] due to [configQualifier]

Explanation

The server no longer meets the qualification requirements of the service profile. This fault typically occurs as a result of one of the following issues:

- The server has been physically changed.

- A required component of the server has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the server inventory compare to the service profile qualifications.

Step 2 If the server inventory does not match the service profile qualifications, do one of the following:

– Associate the server with a different service profile.

– Ensure the server has sufficient resources to qualify for the current service profile.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: server-failed

mibFaultCode: 337

mibFaultName: fltLsServerServerUnfulfilled

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltEtherSwitchIntFIoSatellite-connection-absent

Fault Code: F0367

Message

No link between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]

Explanation

This fault is raised when an I/O module fabric port, which links the I/O module port and the fabric interconnect, is not functional

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the fabric interconnect-chassis topology. Make sure each I/O module is connected to only one fabric interconnect.

Step 2 Ensure that the fabric interconnect server port is configured and enabled.

Step 3 Ensure that the links are plugged in properly and reacknowledge the chassis.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: satellite-connection-absent

mibFaultCode: 367

mibFaultName: fltEtherSwitchIntFIoSatelliteConnectionAbsent

moClass: ether:SwitchIntFIo

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltEtherSwitchIntFIoSatellite-wiring-problem

Fault Code: F0368

Message

Invalid connection between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]

Explanation

This fault typically occurs as a result of a satellite wiring problem on the network-facing interface of an I/O module and Cisco FPR Manager detects that at least one IOM uplink is misconnected to one of the fabric interconnect ports.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the fabric interconnect-chassis topology. Make sure each I/O module is connected to only one fabric interconnect.

Step 2 Ensure that the links are plugged in properly and re-acknowledge the chassis.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: satellite-mis-connected

mibFaultCode: 368

mibFaultName: fltEtherSwitchIntFIoSatelliteWiringProblem

moClass: ether:SwitchIntFIo

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltEquipmentPsuPowerSupplyProblem

Fault Code: F0369

Message

Power supply [id] in chassis [id] power: [power]Power supply [id] in fabric interconnect [id] power: [power]Power supply [id] in fex [id] power: [power]Power supply [id] in server [id] power: [power]

Explanation

This fault typically occurs when Cisco FPR Manager detects a problem with a power supply unit in a chassis, fabric interconnect or a FEX. For example, the PSU is not functional.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the power cord is properly connected to the PSU and the power source.

Step 2 Verify that the power source is 220 volts.

Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

Step 4 Remove the PSU and reinstall it.

Step 5 Replace the PSU.

Step 6 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-problem

mibFaultCode: 369

mibFaultName: fltEquipmentPsuPowerSupplyProblem

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentFanDegraded

Fault Code: F0371

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] operability: [operability]Fan [id] in fabric interconnect [id] operability: [operability]Fan [id] in fex [id] operability: [operability]Fan [id] in Fan Module [tray]-[id] under server [id] operability: [operability]

Explanation

This fault occurs when one or more fans in a fan module are not operational, but at least one fan is operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco FPR Site Preparation Guide and ensure the fan module has adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty fan modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 371

mibFaultName: fltEquipmentFanDegraded

moClass: equipment:Fan

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentFanInoperable

Fault Code: F0373

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] operability: [operability]Fan [id] in fabric interconnect [id] operability: [operability]Fan [id] in fex [id] operability: [operability]Fan [id] in Fan Module [tray]-[id] under server [id] operability: [operability]

Explanation

This fault occurs if a fan is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove fan module and re-install the fan module again. Remove only one fan module at a time.

Step 2 Replace fan module with a different fan module

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 373

mibFaultName: fltEquipmentFanInoperable

moClass: equipment:Fan

Type: equipment

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentPsuInoperable

Fault Code: F0374

Message

Power supply [id] in chassis [id] operability: [operability]Power supply [id] in fabric interconnect [id] operability: [operability]Power supply [id] in fex [id] operability: [operability]Power supply [id] in server [id] operability: [operability]

Explanation

This fault typically occurs when Cisco FPR Manager detects a problem with a power supply unit in a chassis, fabric interconnect or a FEX. For example, the PSU is not functional.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the power cord is properly connected to the PSU and the power source.

Step 2 Verify that the power source is 220 volts.

Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

Step 4 Remove the PSU and reinstall it.

Step 5 Replace the PSU.

Step 6 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 374

mibFaultName: fltEquipmentPsuInoperable

moClass: equipment:Psu

Type: equipment

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentIOCardRemoved

Fault Code: F0376

Message

[side] IOM [chassisId]/[id] ([switchId]) is removed

Explanation

This fault typically occurs because an I/O module is removed from the chassis. In a cluster configuration, the chassis fails over to the other I/O module. For a standalone configuration, the chassis associated with the I/O module loses network connectivity. This is a critical fault because it can result in the loss of network connectivity and disrupt data traffic through the I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reinsert the I/O module and configure the fabric-interconnect ports connected to it as server ports and wait a few minutes to see if the fault clears.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-removed

mibFaultCode: 376

mibFaultName: fltEquipmentIOCardRemoved

moClass: equipment:IOCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentFanModuleMissing

Fault Code: F0377

Message

Fan module [tray]-[id] in chassis [id] presence: [presence]Fan module [tray]-[id] in server [id] presence: [presence]Fan module [tray]-[id] in fabric interconnect [id] presence: [presence]

Explanation

This fault occurs if a fan Module slot is not equipped or removed from its slot

Recommended Action

If you see this fault, take the following actions:

Step 1 If the reported slot is empty, insert a fan module into the slot.

Step 2 If the reported slot contains a fan module, remove and reinsert the fan module.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-missing

mibFaultCode: 377

mibFaultName: fltEquipmentFanModuleMissing

moClass: equipment:FanModule

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentPsuMissing

Fault Code: F0378

Message

Power supply [id] in chassis [id] presence: [presence]Power supply [id] in fabric interconnect [id] presence: [presence]Power supply [id] in fex [id] presence: [presence]Power supply [id] in server [id] presence: [presence]

Explanation

This fault typically occurs when Cisco FPR Manager detects a problem with a power supply unit in a chassis, fabric interconnect, or a FEX. For example, the PSU is missing.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the PSU is physically present in the slot, remove and then reinsert it.

Step 2 If the PSU is not physically present in the slot, insert a new PSU.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-missing

mibFaultCode: 378

mibFaultName: fltEquipmentPsuMissing

moClass: equipment:Psu

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentIOCardThermalProblem

Fault Code: F0379

Message

[side] IOM [chassisId]/[id] ([switchId]) operState: [operState]

Explanation

This fault occurs when there is a thermal problem on an I/O module. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 379

mibFaultName: fltEquipmentIOCardThermalProblem

moClass: equipment:IOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentFanModuleThermalThresholdNonCritical

Fault Code: F0380

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 380

mibFaultName: fltEquipmentFanModuleThermalThresholdNonCritical

moClass: equipment:FanModule

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentPsuThermalThresholdNonCritical

Fault Code: F0381

Message

Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a PSU module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the PSU module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the PSU modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty PSU modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 381

mibFaultName: fltEquipmentPsuThermalThresholdNonCritical

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentFanModuleThermalThresholdCritical

Fault Code: F0382

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 382

mibFaultName: fltEquipmentFanModuleThermalThresholdCritical

moClass: equipment:FanModule

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentPsuThermalThresholdCritical

Fault Code: F0383

Message

Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a PSU module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the PSU module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the PSU modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty PSU modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 383

mibFaultName: fltEquipmentPsuThermalThresholdCritical

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentFanModuleThermalThresholdNonRecoverable

Fault Code: F0384

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has been out of operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 384

mibFaultName: fltEquipmentFanModuleThermalThresholdNonRecoverable

moClass: equipment:FanModule

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentPsuThermalThresholdNonRecoverable

Fault Code: F0385

Message

Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a PSU module has been out of operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the PSU module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the PSU modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty PSU modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 385

mibFaultName: fltEquipmentPsuThermalThresholdNonRecoverable

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuVoltageThresholdNonCritical

Fault Code: F0387

Message

Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

Explanation

This fault occurs when the PSU voltage is out of normal operating range, but hasn’t reached to a critical stage yet. Normally the PSU will recover itself from this situation.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU for further degradation.

Step 2 Remove and reseat the PSU.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: voltage-problem

mibFaultCode: 387

mibFaultName: fltEquipmentPsuVoltageThresholdNonCritical

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuVoltageThresholdCritical

Fault Code: F0389

Message

Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

Explanation

This fault occurs when the PSU voltage has exceeded the specified hardware voltage rating.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reseat the PSU.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 389

mibFaultName: fltEquipmentPsuVoltageThresholdCritical

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuVoltageThresholdNonRecoverable

Fault Code: F0391

Message

Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

Explanation

This fault occurs when the PSU voltage has exceeded the specified hardware voltage rating and PSU hardware may have been damaged as a result or may be at risk of being damaged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reseat the PSU.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: voltage-problem

mibFaultCode: 391

mibFaultName: fltEquipmentPsuVoltageThresholdNonRecoverable

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuPerfThresholdNonCritical

Fault Code: F0392

Message

Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

Explanation

This fault is raised as a warning if the current output of the PSU in a chassis, fabric interconnect, or rack server does not match the desired output value.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU status.

Step 2 If possible, remove and reseat the PSU.

Step 3 If the above action did not resolve the issue, create a show tech-support file for the chassis and Cisco FPR Manager, and contact Cisco TAC.

Fault Details

Severity: minor

Cause: performance-problem

mibFaultCode: 392

mibFaultName: fltEquipmentPsuPerfThresholdNonCritical

moClass: equipment:Psu

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuPerfThresholdCritical

Fault Code: F0393

Message

Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

Explanation

This fault occurs if the current output of the PSU in a chassis, fabric interconnect, or rack server is far below or above the desired output value.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU status.

Step 2 Plan to replace the PSU as soon as possible.

Step 3 If the above actions did not resolve the issue, create a show tech-support file for the chassis and Cisco FPR Manager, and contact Cisco TAC.

Fault Details

Severity: major

Cause: performance-problem

mibFaultCode: 393

mibFaultName: fltEquipmentPsuPerfThresholdCritical

moClass: equipment:Psu

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuPerfThresholdNonRecoverable

Fault Code: F0394

Message

Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

Explanation

This fault occurs if the current output of the PSU in a chassis, fabric interconnect, or rack server is far above or below the non-recoverable threshold value.

Recommended Action

If you see this fault, plan to replace the PSU as soon as possible.

Fault Details

Severity: critical

Cause: performance-problem

mibFaultCode: 394

mibFaultName: fltEquipmentPsuPerfThresholdNonRecoverable

moClass: equipment:Psu

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentFanPerfThresholdNonCritical

Fault Code: F0395

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed reading from the fan controller does not match the desired fan speed and is outside of the normal operating range. This can indicate a problem with a fan or with the reading from the fan controller.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

Step 2 If the problem persists for a long period of time or if other fans do not show the same problem, reseat the fan.

Step 3 Replace the fan module.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: performance-problem

mibFaultCode: 395

mibFaultName: fltEquipmentFanPerfThresholdNonCritical

moClass: equipment:Fan

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentFanPerfThresholdCritical

Fault Code: F0396

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed read from the fan controller does not match the desired fan speed and has exceeded the critical threshold and is in risk of failure. This can indicate a problem with a fan or with the reading from the fan controller.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

Step 2 If the problem persists for a long period of time or if other fans do not show the same problem, reseat the fan.

Step 3 If the above actions did not resolve the issue, create a show tech-support file for the chassis and contact Cisco TAC.

Fault Details

Severity: info

Cause: performance-problem

mibFaultCode: 396

mibFaultName: fltEquipmentFanPerfThresholdCritical

moClass: equipment:Fan

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentFanPerfThresholdNonRecoverable

Fault Code: F0397

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed read from the fan controller has far exceeded the desired fan speed. It frequently indicates that the fan has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Replace the fan.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: performance-problem

mibFaultCode: 397

mibFaultName: fltEquipmentFanPerfThresholdNonRecoverable

moClass: equipment:Fan

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentIOCardFirmwareUpgrade

Fault Code: F0398

Message

Chassis controller in IOM [chassisId]/[id] ([switchId]) firmware upgrade problem: [upgradeStatus]

Explanation

This fault typically occurs when an IOM upgrade fails.

Recommended Action

If you see this fault, take the following actions:

Step 1 On the FSM tab for the IOM, verify whether FSM for the upgrade completed successfully or failed.

Step 2 If the FSM failed, review the error message in the FSM.

Step 3 If the error message is self explanatory, verify the physical connectivity. For example, an error message could be No Connection to Endpoint or Link Down.

Step 4 If the above action did not resolve the issue and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: firmware-upgrade-problem

mibFaultCode: 398

mibFaultName: fltEquipmentIOCardFirmwareUpgrade

moClass: equipment:IOCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentChassisUnsupportedConnectivity

Fault Code: F0399

Message

Current connectivity for chassis [id] does not match discovery policy: [configState]

Explanation

This fault typically occurs when the current connectivity for a chassis does not match the configuration in the chassis discovery policy.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the correct number of links are configured in the chassis discovery policy.

Step 2 Check the state of the I/O module links.

Step 3 Reacknowledge the chassis.

Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: unsupported-connectivity-configuration

mibFaultCode: 399

mibFaultName: fltEquipmentChassisUnsupportedConnectivity

moClass: equipment:Chassis

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentChassisUnacknowledged

Fault Code: F0400

Message

Chassis [id] connectivity configuration: [configState]

Explanation

This fault typically occurs when or more of the I/O module links from the chassis are unacknowledged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state of the I/O module links.

Step 2 Reacknowledge the chassis.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-unacknowledged

mibFaultCode: 400

mibFaultName: fltEquipmentChassisUnacknowledged

moClass: equipment:Chassis

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentIOCardUnsupportedConnectivity

Fault Code: F0401

Message

IOM [chassisId]/[id] ([switchId]) current connectivity does not match discovery policy or connectivity is unsupported: [configState]

Explanation

This fault typically occurs when the current connectivity for an I/O module does not match the configuration in the chassis discovery policy.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the correct number of links are configured in the chassis discovery policy.

Step 2 Check the state of the I/O module links.

Step 3 Note that atleast 2 links are required to be connected between FEX and 61xx Fabric Interconnect

Step 4 Reacknowledge the chassis.

Step 5 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: unsupported-connectivity-configuration

mibFaultCode: 401

mibFaultName: fltEquipmentIOCardUnsupportedConnectivity

moClass: equipment:IOCard

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardUnacknowledged

Fault Code: F0402

Message

IOM [chassisId]/[id] ([switchId]) connectivity configuration: [configState]

Explanation

This fault typically occurs when an I/O module is unacknowledged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state of the I/O module links.

Step 2 Reacknowledge the chassis.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-unacknowledged

mibFaultCode: 402

mibFaultName: fltEquipmentIOCardUnacknowledged

moClass: equipment:IOCard

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardPeerDisconnected

Fault Code: F0403

Message

IOM [chassisId]/[id] ([switchId]) peer connectivity: [peerCommStatus]

Explanation

This fault typically occurs when an I/O module is unable to communicate with its peer I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the fault does not clear after a few minutes, remove and reinsert the I/O module.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-disconnected

mibFaultCode: 403

mibFaultName: fltEquipmentIOCardPeerDisconnected

moClass: equipment:IOCard

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentChassisIdentity

Fault Code: F0404

Message

Chassis [id] has a mismatch between FRU identity reported by Fabric/IOM vs. FRU identity reported by CMC

Explanation

This fault typically occurs when the FRU information for an I/O module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 404

mibFaultName: fltEquipmentChassisIdentity

moClass: equipment:Chassis

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentIOCardIdentity

Fault Code: F0405

Message

[side] IOM [chassisId]/[id] ([switchId]) has a malformed FRU

Explanation

This fault typically occurs when the FRU information for an I/O module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 405

mibFaultName: fltEquipmentIOCardIdentity

moClass: equipment:IOCard

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentFanModuleIdentity

Fault Code: F0406

Message

Fan Module [tray]-[id] in chassis [id] has a malformed FRUFan Module [tray]-[id] in server [id] has a malformed FRUFan Module [tray]-[id] in fabric interconnect [id] has a malformed FRU

Explanation

This fault typically occurs when the FRU information for a fan module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 406

mibFaultName: fltEquipmentFanModuleIdentity

moClass: equipment:FanModule

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentPsuIdentity

Fault Code: F0407

Message

Power supply [id] on chassis [id] has a malformed FRUPower supply [id] on server [id] has a malformed FRU

Explanation

This fault typically occurs when the FRU information for a power supply unit is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 407

mibFaultName: fltEquipmentPsuIdentity

moClass: equipment:Psu

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentChassisPowerProblem

Fault Code: F0408

Message

Power state on chassis [id] is [power]

Explanation

This fault typically occurs when the chassis fails to meet the minimal power requirements defined in the power policy or when one or more power supplies have failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco FPR Manager, verify that all PSUs for the chassis are functional.

Step 2 Verify that all PSUs are seated properly within the chassis and are powered on.

Step 3 Physically unplug and replug the power cord into the chassis.

Step 4 If all PSUs are operating at maximum capacity, either add more PSUs to the chassis or redefine the power policy in Cisco FPR Manager.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-problem

mibFaultCode: 408

mibFaultName: fltEquipmentChassisPowerProblem

moClass: equipment:Chassis

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentChassisThermalThresholdCritical

Fault Code: F0409

Message

Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation

This fault occurs under the following conditions:

Step 1 If a component within a chassis is operating outside the safe thermal operating range.

Step 2 If the chassis controller in the IOM is unable to determine the thermal condition of a blade server, the show tech-support file for the chassis provides a more detailed report of the most severe thermal conditions currently applicable for that chassis.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the temperature readings for the blade servers and IOM and ensure they are within the recommended thermal safe operating range.

Step 2 If the fault reports a "Thermal Sensor threshold crossing in blade" error for one or more blade servers, check if DIMM or processor temperature related faults have been raised against that blade.

Step 3 If the fault reports a "Thermal Sensor threshold crossing in IOM" error for one or both the IOMs, check if thermal faults have been raised against that IOM. Those faults include details of the thermal condition.

Step 4 If the fault reports a "Missing or Faulty Fan" error, check on the status of that fan. If it needs replacement, create a show tech-support file for the chassis and contact Cisco TAC.

Step 5 If the fault reports a "No connectivity between IOM and blade" or "Thermal Sensor readings unavailable from blade" error, check if that blade server is operational and whether any faults have been raised against that blade server. In this situation, the chassis controller may go into a fail-safe operating mode and the fan speeds may increase as a precautionary measure.

Step 6 If the above actions did not resolve the issue and the condition persists, create a show tech-support file for Cisco FPR Manager and the chassis and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 409

mibFaultName: fltEquipmentChassisThermalThresholdCritical

moClass: equipment:Chassis

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentChassisThermalThresholdNonRecoverable

Fault Code: F0411

Message

Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation

FPRM raises this fault under the following conditions:

Step 1 If a component within a chassis is operating outside the safe thermal operating range.

Step 2 If the chassis controller in the IOM is unable to determine the thermal condition of a blade server, the show tech-support file for the chassis provides a more detailed report of the most severe thermal conditions currently applicable for that chassis.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the temperature readings for the blade servers and IOM and ensure they are within the recommended thermal safe operating range.

Step 2 If the fault reports a "Thermal Sensor threshold crossing in blade" error for one or more blade servers, check if DIMM or processor temperature related faults have been raised against that blade.

Step 3 If the fault reports a "Thermal Sensor threshold crossing in IOM" error for one or both the IOMs, check if thermal faults have been raised against that IOM. Those faults include details of the thermal condition.

Step 4 If the fault reports a "Missing or Faulty Fan" error, check on the status of that fan. If it needs replacement, create a show tech-support file for the chassis and contact Cisco TAC.

Step 5 If the fault reports a "No connectivity between IOM and blade" or "Thermal Sensor readings unavailable from blade" error, check if that blade server is operational and whether any faults have been raised against that blade server. In this situation, the chassis controller may go into a fail-safe operating mode and the fan speeds may increase as a precautionary measure.

Step 6 If the above actions did not resolve the issue and the condition persists, create a show tech-support file for Cisco FPR Manager and the chassis and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 411

mibFaultName: fltEquipmentChassisThermalThresholdNonRecoverable

moClass: equipment:Chassis

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltComputeBoardCmosVoltageThresholdCritical

Fault Code: F0424

Message

Possible loss of CMOS settings: CMOS battery voltage on server [chassisId]/[slotId] is [cmosVoltage]Possible loss of CMOS settings: CMOS battery voltage on server [id] is [cmosVoltage]

Explanation

This fault is raised when the CMOS battery voltage has dropped to lower than the normal operating range. This could impact the clock and other CMOS settings.

Recommended Action

If you see this fault, replace the battery.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 424

mibFaultName: fltComputeBoardCmosVoltageThresholdCritical

moClass: compute:Board

Type: environmental

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/rack-unit-[id]/board

fltComputeBoardCmosVoltageThresholdNonRecoverable

Fault Code: F0425

Message

Possible loss of CMOS settings: CMOS battery voltage on server [chassisId]/[slotId] is [cmosVoltage]Possible loss of CMOS settings: CMOS battery voltage on server [id] is [cmosVoltage]

Explanation

This fault is raised when the CMOS battery voltage has dropped quite low and is unlikely to recover. This impacts the clock and other CMOS settings.

Recommended Action

If you see this fault, replace the battery.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 425

mibFaultName: fltComputeBoardCmosVoltageThresholdNonRecoverable

moClass: compute:Board

Type: environmental

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/rack-unit-[id]/board

fltMgmtEntityElection-failure

Fault Code: F0428

Message

Fabric Interconnect [id], election of primary managemt instance has failed

Explanation

This fault occurs in an unlikely event that the fabric interconnects in a cluster configuration could not reach an agreement for selecting the primary fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 In the Cisco FPR Manager CLI, run the cluster force primary local-mgmt command on one fabric interconnect.

Step 4 Reboot the fabric interconnects.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: election-failure

mibFaultCode: 428

mibFaultName: fltMgmtEntityElectionFailure

moClass: mgmt:Entity

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityHa-not-ready

Fault Code: F0429

Message

Fabric Interconnect [id], HA functionality not ready

Explanation

This fault occurs if Cisco FPR Manager cannot discover or communicate with one or more chassis or rack servers to write the HA Cluster state. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Verify that the IOMs and/or FEXes are reachable and the server ports are enabled and operationally up.

Step 4 Verify that the chassis and/or rack servers are powered up and reachable

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: ha-not-ready

mibFaultCode: 429

mibFaultName: fltMgmtEntityHaNotReady

moClass: mgmt:Entity

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityVersion-incompatible

Fault Code: F0430

Message

Fabric Interconnect [id], management services, incompatible versions

Explanation

This fault occurs if the Cisco FPR Manager software on the subordinate fabric interconnect is not the same release as that of the primary fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Upgrade the Cisco FPR Manager software on the subordinate fabric interconnect to the same release as the primary fabric interconnect and verify that both fabric interconnects are running the same release of Cisco FPR Manager.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: version-incompatible

mibFaultCode: 430

mibFaultName: fltMgmtEntityVersionIncompatible

moClass: mgmt:Entity

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltEquipmentFanMissing

Fault Code: F0434

Message

Fan [id] in fabric interconnect [id] presence: [presence]Fan [id] in fex [id] presence: [presence]Fan [id] in Fan Module [tray]-[id] under server [id] presence: [presence]

Explanation

This fault occurs in the unlikely event that a fan in a fan module cannot be detected.

Recommended Action

If you see this fault, take the following actions:

Step 1 Insert/reinsert the fan module in the slot that is reporting the issue.

Step 2 Replace the fan module with a different fan module, if available.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-missing

mibFaultCode: 434

mibFaultName: fltEquipmentFanMissing

moClass: equipment:Fan

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltEquipmentIOCardAutoUpgradingFirmware

Fault Code: F0435

Message

IOM [chassisId]/[id] ([switchId]) is auto upgrading firmware

Explanation

This fault typically occurs when an I/O module is auto upgrading. Auto-upgrade occurs when the firmware version on the IOM is incompatible with the firmware version on the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the IOM and fabric interconnects are not running the same firmware version, wait for the auto-upgrade to complete.

Step 2 When the IOM upgrade is completed, verify that Cisco FPR Manager has cleared this fault.

Step 3 If you see this fault after the IOM overall status changes to operable, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: auto-firmware-upgrade

mibFaultCode: 435

mibFaultName: fltEquipmentIOCardAutoUpgradingFirmware

moClass: equipment:IOCard

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltFirmwarePackItemImageMissing

Fault Code: F0436

Message

[type] image with vendor [hwVendor], model [hwModel] and version [version] is deleted

Explanation

This fault typically occurs when the image to which a firmware package item refers is missing.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco FPR Manager GUI, navigate to the Firmware Management Images tab and determine whether the missing image is available or not.

Step 2 If the image is present, click on it to verify the model and vendor.

Step 3 If the image for the required model and vendor is not present, download that image or bundle from the Cisco.com website.

Step 4 If the image is present and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: image-deleted

mibFaultCode: 436

mibFaultName: fltFirmwarePackItemImageMissing

moClass: firmware:PackItem

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-catalog-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]

Affected MO: org-[name]/fw-host-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]

Affected MO: org-[name]/fw-infra-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]

Affected MO: org-[name]/fw-mgmt-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]

Affected MO: org-[name]/fw-platform-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]

Affected MO: org-[name]/pack-image-[hwVendor]|[hwModel]|[type]

fltEtherSwitchIntFIoSatellite-wiring-numbers-unexpected

Fault Code: F0440

Message

Chassis discovery policy conflict: Link IOM [chassisId]/[slotId]/[portId] to fabric interconnect [switchId]:[peerSlotId]/[peerPortId] not configured

Explanation

The configuration of the chassis discovery policy conflicts with the physical IOM uplinks. Cisco FPR Manager raises this fault when the chassis discovery policy is configured for more links than are physically cabled between the IOM uplinks on the chassis and the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure that you cable at least the same number of IOM uplinks as are configured in the chassis discovery policy, and that you configure the corresponding server ports on the fabric interconnect.

Step 2 Reacknowledge the chassis.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: unexpected-number-of-links

mibFaultCode: 440

mibFaultName: fltEtherSwitchIntFIoSatelliteWiringNumbersUnexpected

moClass: ether:SwitchIntFIo

Type: connectivity

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltMgmtEntityManagement-services-failure

Fault Code: F0451

Message

Fabric Interconnect [id], management services have failed

Explanation

This fault occurs in an unlikely event that management services fail on a fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Reboot the fabric interconnects.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: management-services-failure

mibFaultCode: 451

mibFaultName: fltMgmtEntityManagementServicesFailure

moClass: mgmt:Entity

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityManagement-services-unresponsive

Fault Code: F0452

Message

Fabric Interconnect [id], management services are unresponsive

Explanation

This fault occurs when management services on a fabric interconnect are unresponsive. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Reboot the fabric interconnects.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: management-services-unresponsive

mibFaultCode: 452

mibFaultName: fltMgmtEntityManagementServicesUnresponsive

moClass: mgmt:Entity

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltEquipmentChassisInoperable

Fault Code: F0456

Message

Chassis [id] operability: [operability]

Explanation

This fault typically occurs for one of the following reasons:

- The fabric interconnect cannot communicate with a chassis. For a cluster configuration, this fault means that neither fabric interconnect can communicate with the chassis.

- The chassis has an invalid FRU.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco FPR Manager, reacknowledge the chassis that raised the fault.

Step 2 Physically unplug and replug the power cord into the chassis.

Step 3 Verify that the I/O modules are functional.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 456

mibFaultName: fltEquipmentChassisInoperable

moClass: equipment:Chassis

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEtherServerIntFIoHardware-failure

Fault Code: F0458

Message

IOM [transport] interface [portId] on chassis [id] oper state: [operState], reason: [stateQual]Fabric Interconnect [transport] interface [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]IOM [transport] interface [portId] on fex [id] oper state: [operState], reason: [stateQual]

Explanation

This fault is raised on the IOM/FEX backplane ports when Cisco FPR Manager detects a hardware failure.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: interface-failed

mibFaultCode: 458

mibFaultName: fltEtherServerIntFIoHardwareFailure

moClass: ether:ServerIntFIo

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/rack-unit-[id]/diag/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltDcxVcMgmt-vif-down

Fault Code: F0459

Message

IOM [chassisId] / [slotId] ([switchId]) management VIF [id] down, reason [stateQual]

Explanation

This fault occurs when the transport VIF for an I/O module is down. Cisco FPR Manager raises this fault when a fabric interconnect reports the connectivity state on virtual interface as one of the following:

- Down

- Errored

- Unavailable

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the chassis discovery has gone through successfully. Check the states on all communicating ports from end to end.

Step 2 If connectivity seems correct, decommission and recommission the chassis.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: cmc-vif-down

mibFaultCode: 459

mibFaultName: fltDcxVcMgmtVifDown

moClass: dcx:Vc

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/vc-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/switch-[id]/ethlanflowmon/vc-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vc-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/vc-[id]

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]/vc-[id]

fltSysdebugMEpLogMEpLogLog

Fault Code: F0460

Message

Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the system event log (SEL) on the server is approaching full capacity. The available capacity in the log is low. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action

If you see this fault, you can clear the SEL in Cisco FPR Manager if desired.

Fault Details

Severity: info

Cause: log-capacity

mibFaultCode: 460

mibFaultName: fltSysdebugMEpLogMEpLogLog

moClass: sysdebug:MEpLog

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]

Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltSysdebugMEpLogMEpLogVeryLow

Fault Code: F0461

Message

Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the system event log (SEL) on the server is almost full. The available capacity in the log is very low. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action

If you see this fault, you can clear the SEL in Cisco FPR Manager if desired.

Fault Details

Severity: info

Cause: log-capacity

mibFaultCode: 461

mibFaultName: fltSysdebugMEpLogMEpLogVeryLow

moClass: sysdebug:MEpLog

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]

Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltSysdebugMEpLogMEpLogFull

Fault Code: F0462

Message

Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

Explanation

This fault typically occurs because Cisco FPR Manager could not transfer the SEL file to the location specified in the SEL policy. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the configuration of the SEL policy to ensure that the location, user, and password provided are correct.

Step 2 If you do want to transfer and clear the SEL and the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: log-capacity

mibFaultCode: 462

mibFaultName: fltSysdebugMEpLogMEpLogFull

moClass: sysdebug:MEpLog

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]

Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltComputePoolEmpty

Fault Code: F0463

Message

server pool [name] is empty

Explanation

This fault typically occurs when the selected server pool does not contain any servers.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the qualifier settings in the server pool policy qualifications. If the policy was modified after the server was discovered, reacknowledge the server.

Step 2 Manually associate the service profile with a server.

Step 3 If the server pool is not used, ignore the fault.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 463

mibFaultName: fltComputePoolEmpty

moClass: compute:Pool

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/compute-pool-[name]

fltUuidpoolPoolEmpty

Fault Code: F0464

Message

UUID suffix pool [name] is empty

Explanation

This fault typically occurs when a UUID suffix pool does not contain any UUID suffixes.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the pool is in use, add a block of UUID suffixes to the pool.

Step 2 If the pool is not in use, ignore the fault.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 464

mibFaultName: fltUuidpoolPoolEmpty

moClass: uuidpool:Pool

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/uuid-pool-[name]

fltIppoolPoolEmpty

Fault Code: F0465

Message

IP pool [name] is empty

Explanation

This fault typically occurs when an IP address pool does not contain any IP addresses.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the pool is in use, add a block of IP addresses to the pool.

Step 2 If the pool is not in use, ignore the fault.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 465

mibFaultName: fltIppoolPoolEmpty

moClass: ippool:Pool

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets/ip-pool-[name]

Affected MO: org-[name]/ip-pool-[name]

fltMacpoolPoolEmpty

Fault Code: F0466

Message

MAC pool [name] is empty

Explanation

This fault typically occurs when a MAC address pool does not contain any MAC addresses.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the pool is in use, add a block of MAC addresses to the pool.

Step 2 If the pool is not in use, ignore the fault.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 466

mibFaultName: fltMacpoolPoolEmpty

moClass: macpool:Pool

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/mac-pool-[name]

fltFirmwareUpdatableImageUnusable

Fault Code: F0470

Message

backup image is unusable. reason: [operStateQual]

Explanation

This fault typically occurs when the backup firmware image on an endpoint is unusable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the fault and the error message on the FSM tab for the endpoint to determine why the firmware image is unusable.

Step 2 If the firmware image is bad or corrupted, download another copy from the Cisco website and update the backup version on the endpoint with the new image.

Step 3 If the image is present and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: image-unusable

mibFaultCode: 470

mibFaultName: fltFirmwareUpdatableImageUnusable

moClass: firmware:Updatable

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-updatable

Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-updatable

Affected MO: sys/chassis-[id]/fpga/fw-updatable

Affected MO: sys/chassis-[id]/rommon/fw-updatable

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-updatable

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-updatable

Affected MO: sys/fex-[id]/mgmt/fw-updatable

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-updatable

Affected MO: sys/mgmt/fw-updatable

Affected MO: sys/os-ctrl/fw-updatable

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-updatable

Affected MO: sys/rack-unit-[id]/bios/fw-updatable

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-updatable

Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-updatable

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-updatable

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-updatable

Affected MO: sys/rack-unit-[id]/mgmt/fw-updatable

Affected MO: sys/rack-unit-[id]/os-ctrl/fw-updatable

Affected MO: sys/switch-[id]/mgmt/fw-updatable

fltFirmwareBootUnitCantBoot

Fault Code: F0471

Message

unable to boot the startup image. End point booted with backup image

Explanation

This fault typically occurs when the startup firmware image on an endpoint is corrupted or invalid, and the endpoint cannot boot from that image.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the fault and the error message on the FSM tab for the endpoint to determine why the firmware image is unusable. The error message usually includes an explanation for why the endpoint could not boot from the startup image, such as Bad-Image or Checksum Failed.

Step 2 If the firmware image is bad or corrupted, download another copy from the Cisco website and update the startup version on the endpoint with the new image.

Step 3 If the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: image-cannot-boot

mibFaultCode: 471

mibFaultName: fltFirmwareBootUnitCantBoot

moClass: firmware:BootUnit

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext/fw-boot-def/bootunit-[type]

Affected MO: capabilities/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/fpga/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/rommon/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/switch-[id]/mgmt/fw-boot-def/bootunit-[type]

fltFcpoolInitiatorsEmpty

Fault Code: F0476

Message

FC pool [purpose] [name] is empty

Explanation

This fault typically occurs when a WWN pool does not contain any WWNs.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the pool is in use, add a block of WWNs to the pool.

Step 2 If the pool is not in use, ignore the fault.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 476

mibFaultName: fltFcpoolInitiatorsEmpty

moClass: fcpool:Initiators

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/wwn-pool-[name]

fltEquipmentIOCardInaccessible

Fault Code: F0478

Message

[side] IOM [chassisId]/[id] ([switchId]) is inaccessible

Explanation

This fault typically occurs because an I/O module has lost its connection to the fabric interconnects. In a cluster configuration, the chassis fails over to the other I/O module. For a standalone configuration, the chassis associated with the I/O module loses network connectivity. This is a critical fault because it can result in the loss of network connectivity and disrupt data traffic through the I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inaccessible

mibFaultCode: 478

mibFaultName: fltEquipmentIOCardInaccessible

moClass: equipment:IOCard

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltDcxVIfLinkState

Fault Code: F0479

Message

Virtual interface [id] link state is down

Explanation

This fault occurs when Cisco FPR cannot send or receive data through an uplink port.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reenable the uplink port that failed.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: vif-down

mibFaultCode: 479

mibFaultName: fltDcxVIfLinkState

moClass: dcx:VIf

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]/vif-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fcoe/vif-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/vif-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fcoe/vif-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/vif-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-service-eth-[id]/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fcoe/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fcoe/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/vif-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-service-eth-[id]/vif-[id]

fltEquipmentFanModuleDegraded

Fault Code: F0480

Message

Fan module [tray]-[id] in chassis [id] operability: [operability]Fan module [tray]-[id] in server [id] operability: [operability]Fan module [tray]-[id] in fabric interconnect [id] operability: [operability]

Explanation

This fault occurs when a fan module is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the fan module has adequate airflow, including front and back clearance.

Step 3 Verify that the air flows for the fan module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 480

mibFaultName: fltEquipmentFanModuleDegraded

moClass: equipment:FanModule

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentIOCardPost-failure

Fault Code: F0481

Message

[side] IOM [chassisId]/[id] ([switchId]) POST failure

Explanation

This fault typically occurs when an I/O module encounters errors during the Power On Self Test (POST). The impact of this fault varies according to the errors that were encountered during POST.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the I/O module. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the I/O module. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the I/O module.

Step 2 If the POST results indicate FRU error, check if FPR manager has raised fault for the FRU and follow recommended action for the fault.

Step 3 Otherwise, reboot the I/O module.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-problem

mibFaultCode: 481

mibFaultName: fltEquipmentIOCardPostFailure

moClass: equipment:IOCard

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentFanPerfThresholdLowerNonRecoverable

Fault Code: F0484

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed reading from the fan controller is far below the desired fan speed, and the fan has likely failed.

Recommended Action

If you see this fault, create a detailed show tech-support file for the chassis and replace the fan module. If necessary, contact Cisco TAC.

Fault Details

Severity: critical

Cause: performance-problem

mibFaultCode: 484

mibFaultName: fltEquipmentFanPerfThresholdLowerNonRecoverable

moClass: equipment:Fan

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/fex-[id]/fan-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltComputePhysicalPost-failure

Fault Code: F0517

Message

Server [id] POST or diagnostic failureServer [chassisId]/[slotId] POST or diagnostic failure

Explanation

This fault typically occurs when the server has encountered a diagnostic failure or an error during POST.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 Reboot the server.

Step 3 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: equipment-problem

mibFaultCode: 517

mibFaultName: fltComputePhysicalPostFailure

moClass: compute:Physical

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltEquipmentPsuOffline

Fault Code: F0528

Message

Power supply [id] in chassis [id] power: [power]Power supply [id] in fabric interconnect [id] power: [power]Power supply [id] in fex [id] power: [power]Power supply [id] in server [id] power: [power]

Explanation

This fault typically occurs when Cisco FPR Manager detects that a power supply unit in a chassis, fabric interconnect, or FEX is offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the power cord is properly connected to the PSU and the power source.

Step 2 Verify that the power source is 220 volts.

Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

Step 4 Remove the PSU and reinstall it.

Step 5 Replace the PSU.

Step 6 If the above actions did not resolve the issue, note down the type of PSU, execute the show tech-support command, and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: equipment-offline

mibFaultCode: 528

mibFaultName: fltEquipmentPsuOffline

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltStorageRaidBatteryInoperable

Fault Code: F0531

Message

RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the RAID backup unit is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the backup unit is a battery, replace the battery.

Step 2 If the backup unit is a supercapacitor type and the supercapacitor is missing, verify its presence and supply if missing.

Step 3 If the backup unit is a supercapacitor type and the TFM is missing, verify its presence and supply if missing.

Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 531

mibFaultName: fltStorageRaidBatteryInoperable

moClass: storage:RaidBattery

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltSysdebugMEpLogTransferError

Fault Code: F0532

Message

Server [chassisId]/[slotId] [type] transfer failed: [operState]Server [id] [type] transfer failed: [operState]

Explanation

This fault occurs when the transfer of a managed endpoint log file, such as the SEL, fails.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault is related to the SEL, verify the connectivity to the CIMC on the server.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: file-transfer-failed

mibFaultCode: 532

mibFaultName: fltSysdebugMEpLogTransferError

moClass: sysdebug:MEpLog

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]

Affected MO: sys/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]

Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]

Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltComputeRtcBatteryInoperable

Fault Code: F0533

Message

RTC Battery on server [chassisId]/[slotId] operability: [operability]

Explanation

This fault is raised when the CMOS battery voltage is below the normal operating range. This impacts the system clock.

Recommended Action

If you see this fault, replace the CMOS battery.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 533

mibFaultName: fltComputeRtcBatteryInoperable

moClass: compute:RtcBattery

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/rtc-battery

Affected MO: sys/rack-unit-[id]/board/rtc-battery

fltMemoryBufferUnitThermalThresholdNonCritical

Fault Code: F0535

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server exceeds a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: thermal-problem

mibFaultCode: 535

mibFaultName: fltMemoryBufferUnitThermalThresholdNonCritical

moClass: memory:BufferUnit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]

Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltMemoryBufferUnitThermalThresholdCritical

Fault Code: F0536

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server exceeds a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 536

mibFaultName: fltMemoryBufferUnitThermalThresholdCritical

moClass: memory:BufferUnit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]

Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltMemoryBufferUnitThermalThresholdNonRecoverable

Fault Code: F0537

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 537

mibFaultName: fltMemoryBufferUnitThermalThresholdNonRecoverable

moClass: memory:BufferUnit

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]

Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltComputeIOHubThermalNonCritical

Fault Code: F0538

Message

IO Hub on server [chassisId]/[slotId] temperature: [thermal]

Explanation

This fault is raised when the IO controller temperature is outside the upper or lower non-critical threshold.

Recommended Action

If you see this fault, monitor other environmental events related to this server and ensure the temperature ranges are within recommended ranges.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 538

mibFaultName: fltComputeIOHubThermalNonCritical

moClass: compute:IOHub

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub

Affected MO: sys/rack-unit-[id]/board/iohub

fltComputeIOHubThermalThresholdCritical

Fault Code: F0539

Message

IO Hub on server [chassisId]/[slotId] temperature: [thermal]

Explanation

This fault is raised when the IO controller temperature is outside the upper or lower critical threshold.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor other environmental events related to the server and ensure the temperature ranges are within recommended ranges.

Step 2 Consider turning off the server for a while if possible.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 539

mibFaultName: fltComputeIOHubThermalThresholdCritical

moClass: compute:IOHub

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub

Affected MO: sys/rack-unit-[id]/board/iohub

fltComputeIOHubThermalThresholdNonRecoverable

Fault Code: F0540

Message

IO Hub on server [chassisId]/[slotId] temperature: [thermal]

Explanation

This fault is raised when the IO controller temperature is outside the recoverable range of operation.

Recommended Action

If you see this fault, take the following actions:

Step 1 Shutdown the server immediately.

Step 2 Create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 540

mibFaultName: fltComputeIOHubThermalThresholdNonRecoverable

moClass: compute:IOHub

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub

Affected MO: sys/rack-unit-[id]/board/iohub

fltEquipmentChassisIdentity-unestablishable

Fault Code: F0543

Message

Chassis [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported chassis. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, execute the show tech-support command and contact Cisco technical support.

Fault Details

Severity: major

Cause: identity-unestablishable

mibFaultCode: 543

mibFaultName: fltEquipmentChassisIdentityUnestablishable

moClass: equipment:Chassis

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltSwVlanPortNsResourceStatus

Fault Code: F0549

Message

Vlan-Port Resource exceeded

Explanation

This fault occurs when the total number of configured VLANs in the Cisco FPR instance has exceeded the allowed maximum number of configured VLANs on the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 In the Cisco FPR Manager CLI or Cisco FPR Manager GUI, check the port VLAN count to determine by how many VLANs the system is over the maximum.

Step 2 Reduce the VLAN port count in one of the following ways:

– Delete VLANs configured on the LAN cloud.

– Delete VLANs configured on vNICs.

– Unconfigure one or more vNICs.

– Unconfigure one or more uplink Ethernet ports on the fabric interconnect.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: limit-reached

mibFaultCode: 549

mibFaultName: fltSwVlanPortNsResourceStatus

moClass: sw:VlanPortNs

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/vlan-port-ns

fltFabricLanPinGroupEmpty

Fault Code: F0621

Message

LAN Pin Group [name] is empty

Explanation

This fault typically occurs when a LAN pin group does not contain any targets.

Recommended Action

If you see this fault, add a target to the LAN pin group.

Fault Details

Severity: minor

Cause: empty-pin-group

mibFaultCode: 621

mibFaultName: fltFabricLanPinGroupEmpty

moClass: fabric:LanPinGroup

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/lan-pin-group-[name]

fltAdaptorExtEthIfMisConnect

Fault Code: F0625

Message

Adapter [id] eth interface [id] in server [id] mis-connected

Explanation

The link for a network-facing adapter interface is misconnected. Cisco FPR Manager raises this fault when any of the following scenarios occur:

- Cisco FPR Manager detects a new connectivity between a previously configured switch port or FEX port and the adapter’s external interface.

- Cisco FPR Manager detects a misconnected link between a fabric interconnect or FEX and its non-peer adapter’s interface.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter link is connected to a port that belongs to its peer fabric interconnect or FEX.

Step 2 If that connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-misconnected

mibFaultCode: 625

mibFaultName: fltAdaptorExtEthIfMisConnect

moClass: adaptor:ExtEthIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fltAdaptorHostEthIfMisConnect

Fault Code: F0626

Message

Adapter [id] eth interface [id] in server [id] mis-connected

Explanation

The link for a network-facing host interface is misconnected. Cisco FPR Manager raises this fault when any of the following scenarios occur:

- Cisco FPR Manager detects a new connectivity between a previously configured switch port and the host Ethernet interface.

- Cisco FPR Manager detects a misconnected link between the host interface and its non-peer fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the host Ethernet interface is connected to a port belonging to its peer fabric interconnect.

Step 2 If connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-misconnected

mibFaultCode: 626

mibFaultName: fltAdaptorHostEthIfMisConnect

moClass: adaptor:HostEthIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fltPowerBudgetPowerBudgetCmcProblem

Fault Code: F0635

Message

Power cap application failed for chassis [id]

Explanation

This fault typically occurs when the server CIMC has failed to enforce the configured power cap.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the power consumption of the chassis. If the chassis is consuming significantly more power than configured in the power cap, consider reducing the group cap so that the power consumption of other chassis consumption can be reduced to make up for the increase.

Step 2 If the above action did not resolve the issue, create a show tech-support file for Cisco FPR Manager and the chassis and then contact Cisco TAC.

Fault Details

Severity: major

Cause: power-cap-fail

mibFaultCode: 635

mibFaultName: fltPowerBudgetPowerBudgetCmcProblem

moClass: power:Budget

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetPowerBudgetBmcProblem

Fault Code: F0637

Message

Power cap application failed for server [chassisId]/[slotId]Power cap application failed for server [id]

Explanation

This fault typically occurs when the server CIMC or BIOS has failed to enforce the configured power cap.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the power consumption of the blade server. If the server is consuming significantly more power than configured in the power cap, switch to a manual per blade cap configuration. If the power consumption is still too high, consider reducing the group cap so that the power consumption of other chassis consumption can be reduced to make up for the increase.

Step 2 If the power consumption is still too high, the CIMC or BIOS software is likely faulty.

Step 3 Create a show tech-support file for Cisco FPR Manager and the chassis and then contact Cisco TAC.

Fault Details

Severity: major

Cause: power-cap-fail

mibFaultCode: 637

mibFaultName: fltPowerBudgetPowerBudgetBmcProblem

moClass: power:Budget

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetPowerBudgetDiscFail

Fault Code: F0640

Message

Insufficient power available to discover server [chassisId]/[slotId]Insufficient power available to discover server [id]

Explanation

This fault typically occurs when discovery fails due to unavailable power in the group.

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider increasing the group cap.

Step 2 Reduce the number of blade servers or chassis in the Cisco FPR instance.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-cap-fail

mibFaultCode: 640

mibFaultName: fltPowerBudgetPowerBudgetDiscFail

moClass: power:Budget

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerGroupPowerGroupInsufficientBudget

Fault Code: F0642

Message

insufficient budget for power group [name]

Explanation

This fault typically occurs when the group cap is insufficient to meet the minimum hardware requirements.

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider increasing the group cap.

Step 2 Reduce the number of blade servers or chassis in the Cisco FPR instance.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-cap-fail

mibFaultCode: 642

mibFaultName: fltPowerGroupPowerGroupInsufficientBudget

moClass: power:Group

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]

fltPowerGroupPowerGroupBudgetIncorrect

Fault Code: F0643

Message

admin committed insufficient for power group [name], using previous value [operCommitted]

Explanation

This fault typically occurs when the group cap is insufficient to meet the minimum hardware requirements. Under these circumstances, Cisco FPR Manager uses the previously entered group cap for provisioning.

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider increasing the group cap.

Step 2 Reduce the number of blade servers or chassis in the Cisco FPR instance.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-cap-fail

mibFaultCode: 643

mibFaultName: fltPowerGroupPowerGroupBudgetIncorrect

moClass: power:Group

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]

fltMgmtIfMisConnect

Fault Code: F0688

Message

Management Port [id] in server [id] is mis connected

Explanation

This fault occurs when the server and FEX connectivity changes.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the connectivity between the server and FEX.

Step 2 If the connectivity was changed by mistake, restore it to its previous configuration.

Step 3 If the connectivity change was intentional, reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-misconnected

mibFaultCode: 688

mibFaultName: fltMgmtIfMisConnect

moClass: mgmt:If

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fltLsComputeBindingAssignmentRequirementsNotMet

Fault Code: F0689

Message

Assignment of service profile [name] to server [pnDn] failed

Explanation

The server could not be assigned to the selected service profile. This fault typically occurs as a result of one of the following issues:

- The selected server does not meet the requirements of the service profile.

- If the service profile was configured for restricted migration, the selected server does not match the currently or previously assigned server.

Recommended Action

If you see this fault, select a different server that meets the requirements of the service profile or matches the currently or previously assigned server.

Fault Details

Severity: minor

Cause: assignment-failed

mibFaultCode: 689

mibFaultName: fltLsComputeBindingAssignmentRequirementsNotMet

moClass: ls:ComputeBinding

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/pn

Affected MO: org-[name]/ls-[name]/pn-req

Affected MO: org-[name]/tier-[name]/ls-[name]/pn

Affected MO: org-[name]/tier-[name]/ls-[name]/pn-req

fltEquipmentFexPost-failure

Fault Code: F0702

Message

fex [id] POST failure

Explanation

This fault typically occurs when a FEX encounters errors during the Power On Self Test (POST). The impact of this fault varies depending on which errors were encountered during POST.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the FEX. In the Cisco FPR Manager GUI, you can access the POST results from the General tab for the FEX. In the Cisco FPR Manager CLI, you can access the POST results by entering the show post command under the scope for the FEX.

Step 2 Reboot the FEX.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-problem

mibFaultCode: 702

mibFaultName: fltEquipmentFexPostFailure

moClass: equipment:Fex

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fltEquipmentFexIdentity

Fault Code: F0703

Message

Fex [id] has a malformed FRU

Explanation

This fault typically occurs when the FRU information for a FEX is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 703

mibFaultName: fltEquipmentFexIdentity

moClass: equipment:Fex

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fltAdaptorHostEthIfMissing

Fault Code: F0708

Message

Connection to Adapter [id] eth interface [id] in server [id] missing

Explanation

The link for a network-facing host interface is missing. Cisco FPR Manager raises this fault when it detects missing connectivity between a previously configured switch port and its previous peer host interface.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter link is connected to a port that belongs to its non-peer fabric interconnect.

Step 2 If that connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-missing

mibFaultCode: 708

mibFaultName: fltAdaptorHostEthIfMissing

moClass: adaptor:HostEthIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fltPortPIoInvalid-sfp

Fault Code: F0713

Message

[transport] port [portId] on chassis [id] role : [ifRole] transceiver type:[xcvrType][transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] role : [ifRole] transceiver type:[xcvrType][transport] port [slotId]/[portId] on fabric interconnect [id] role : [ifRole] transceiver type:[xcvrType]

Explanation

This fault is raised against a fabric interconnect port, network-facing IOM port, or FEX module port if an unsupported transceiver type is inserted. The port cannot be used if it has an unsupported transceiver.

Recommended Action

If you see this fault, replace the transceiver with a supported SFP type. Refer to the documentation on the Cisco website for a list of supported SFPs.

Fault Details

Severity: major

Cause: unsupported-transceiver

mibFaultCode: 713

mibFaultName: fltPortPIoInvalidSfp

moClass: port:PIo

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltMgmtIfMissing

Fault Code: F0717

Message

Connection to Management Port [id] in server [id] is missing

Explanation

This fault occurs when the connectivity between a server and FEX is removed or unconfigured.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the connectivity between the server and FEX.

Step 2 If the connectivity was changed by mistake, restore it to its previous configuration.

Step 3 If the connectivity change was intentional, reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-missing

mibFaultCode: 717

mibFaultName: fltMgmtIfMissing

moClass: mgmt:If

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fltFabricEthLanPcEpDown

Fault Code: F0727

Message

[type] Member [slotId]/[aggrPortId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership][type] Member [slotId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership]

Explanation

This fault typically occurs when a member port in an Ethernet port channel is down.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the link connectivity on the upstream Ethernet switch.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: membership-down

mibFaultCode: 727

mibFaultName: fltFabricEthLanPcEpDown

moClass: fabric:EthLanPcEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltEquipmentIOCardThermalThresholdNonCritical

Fault Code: F0729

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 729

mibFaultName: fltEquipmentIOCardThermalThresholdNonCritical

moClass: equipment:IOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardThermalThresholdCritical

Fault Code: F0730

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 730

mibFaultName: fltEquipmentIOCardThermalThresholdCritical

moClass: equipment:IOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardThermalThresholdNonRecoverable

Fault Code: F0731

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 731

mibFaultName: fltEquipmentIOCardThermalThresholdNonRecoverable

moClass: equipment:IOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentChassisSeeprom-inoperable

Fault Code: F0733

Message

Device [id] SEEPROM operability: [seepromOperState]

Explanation

This fault occurs in the unlikely event that the Chassis shared storage (SEEPROM) is not operational.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 733

mibFaultName: fltEquipmentChassisSeepromInoperable

moClass: equipment:Chassis

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltExtmgmtIfMgmtifdown

Fault Code: F0736

Message

Management interface on Fabric Interconnect [id] is [operState]

Explanation

This fault occurs when a fabric interconnect reports that the operational state of an external management interface is down.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state transitions of the external management interface on the fabric interconnect.

Step 2 Check the link connectivity for the external management interface.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: mgmtif-down

mibFaultCode: 736

mibFaultName: fltExtmgmtIfMgmtifdown

moClass: extmgmt:If

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/extmgmt-intf

fltPowerChassisMemberPowerGroupCapInsufficient

Fault Code: F0740

Message

Chassis [id] cannot be capped as group cap is low. Please consider raising the cap.

Explanation

This fault typically occurs when an updated group cap is insufficient to meet the minimum hardware requirements and a chassis that has just been added to the power group cannot be capped as a result.

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider increasing the group cap.

Step 2 Reduce the number of blade servers or chassis in the Cisco FPR instance.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: group-cap-insufficient

mibFaultCode: 740

mibFaultName: fltPowerChassisMemberPowerGroupCapInsufficient

moClass: power:ChassisMember

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisFirmwareProblem

Fault Code: F0741

Message

Chassis [id] cannot be capped as at least one of the CMC or CIMC or BIOS firmware version is less than 1.4. Please upgrade the firmware for cap to be applied.

Explanation

This fault typically occurs when the CIMC firmware on a server is an earlier release than Cisco FPR, Release 1.4.

Recommended Action

If you see this fault, consider upgrading the CIMC firmware, and the entire Cisco FPR instance if necessary, to Cisco FPR, Release 1.4 or later.

Fault Details

Severity: major

Cause: old-chassis-component-firmware

mibFaultCode: 741

mibFaultName: fltPowerChassisMemberChassisFirmwareProblem

moClass: power:ChassisMember

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisPsuInsufficient

Fault Code: F0742

Message

Chassis [id] cannot be capped as at least two PSU need to be powered

Explanation

This fault typically occurs when at least two PSUs are not powered on.

Recommended Action

If you see this fault, insert at least two PSUs and power them on.

Fault Details

Severity: major

Cause: psu-insufficient

mibFaultCode: 742

mibFaultName: fltPowerChassisMemberChassisPsuInsufficient

moClass: power:ChassisMember

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisPsuRedundanceFailure

Fault Code: F0743

Message

Chassis [id] was configured for redundancy, but running in a non-redundant configuration.

Explanation

This fault typically occurs when chassis power redundancy has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider adding more PSUs to the chassis.

Step 2 Replace any non-functional PSUs.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: psu-redundancy-fail

mibFaultCode: 743

mibFaultName: fltPowerChassisMemberChassisPsuRedundanceFailure

moClass: power:ChassisMember

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerBudgetPowerCapReachedCommit

Fault Code: F0744

Message

P-State lowered as consumption hit power cap for server [chassisId]/[slotId]P-State lowered as consumption hit power cap for server [id]

Explanation

This fault typically occurs when Cisco FPR Manager is actively capping the power for a blade server.

Recommended Action

If you see this fault, no action is needed.

Fault Details

Severity: info

Cause: power-consumption-hit-limit

mibFaultCode: 744

mibFaultName: fltPowerBudgetPowerCapReachedCommit

moClass: power:Budget

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure

Fault Code: F0747

Message

Auto core transfer failure at remote server [hostname]:[path] [exportFailureReason]

Explanation

This fault occurs when Cisco Firepower Manager cannot transfer a core file to a remote TFTP server. This is typically the result of one of the following issues:

- The remote TFTP server is not accessible.

- One or more of the parameters for the TFTP server that are specified for the core export target, such as path, port, and server name, are incorrect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the connectivity to the remote server.

Step 2 Verify the path information of the remote server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: tftp-server-error

mibFaultCode: 747

mibFaultName: fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure

moClass: sysdebug:AutoCoreFileExportTarget

Type: sysdebug

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fltFabricMonSpanConfigFail

Fault Code: F0757

Message

Configuration for traffic monitor [name] failed, reason: [configFailReason]

Explanation

This fault typically occurs when the configuration of a traffic monitoring session is incorrect.

Recommended Action

If you see this fault, correct the configuration problem provided in the fault description.

Fault Details

Severity: major

Cause: config-error

mibFaultCode: 757

mibFaultName: fltFabricMonSpanConfigFail

moClass: fabric:Mon

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lanmon/[id]/eth-mon-[name]

Affected MO: fabric/sanmon/[id]/fc-mon-[name]

fltPowerBudgetChassisPsuInsufficient

Fault Code: F0764

Message

Chassis [id] cannot be capped as the available PSU power is not enough for the chassis and the blades. Please correct the problem by checking input power or replace the PSU

Explanation

This fault typically occurs when the available PSU power is not enough to deploy the power budget of chassis and blades.

Recommended Action

If you see this fault, check the PSU input power or replace the PSU.

Fault Details

Severity: major

Cause: psu-insufficient

mibFaultCode: 764

mibFaultName: fltPowerBudgetChassisPsuInsufficient

moClass: power:Budget

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetTStateTransition

Fault Code: F0765

Message

Blade [chassisId]/[slotId] has been severely throttled. CIMC can recover if budget is redeployed to the blade or by rebooting the blade. If problem persists, please ensure that OS is ACPI compliantRack server [id] has been severely throttled. CIMC can recover if budget is redeployed to the blade or by rebooting the blade. If problem persists, please ensure that OS is ACPI compliant

Explanation

This fault typically occurs when the processor T-state is used to severely throttle the CPU.

Recommended Action

If you see this fault, take the following actions:

Step 1 Redeploy the power budget for the affected power group, blade server, or chassis.

Step 2 If the problem persists, reboot the blade server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: no-ack-from-bios

mibFaultCode: 765

mibFaultName: fltPowerBudgetTStateTransition

moClass: power:Budget

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerPolicyPowerPolicyApplicationFail

Fault Code: F0766

Message

Insufficient budget to apply no-cap priority through policy [name]. Blades will continue to be capped

Explanation

This fault occurs when a power policy cannot be applied to one or more blade servers. The affected blade servers cannot operate normally without power capping due to the limited power budget for those servers.

Recommended Action

If you see this fault, take the following actions:

Step 1 Increase the power budget for the blade servers in the power policy.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: no-cap-fail

mibFaultCode: 766

mibFaultName: fltPowerPolicyPowerPolicyApplicationFail

moClass: power:Policy

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/power-policy-[name]

fltMgmtIfNew

Fault Code: F0772

Message

New connection discovered on Management Port [id] in server [id]

Explanation

This fault occurs when the connectivity between a server and a FEX is added or changed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the connectivity between the server and FEX.

Step 2 If the connectivity was changed by mistake, restore it to its previous configuration.

Step 3 If the connectivity change was intentional, reacknowledge the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: new-link

mibFaultCode: 772

mibFaultName: fltMgmtIfNew

moClass: mgmt:If

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fltAdaptorExtEthIfMissing

Fault Code: F0775

Message

Connection to Adapter [id] eth interface [id] in server [id] missing

Explanation

The link for a network-facing adapter interface is misconnected. Cisco FPR Manager raises this fault when it detects that the connectivity between a previously configured port on a fabric interconnect or FEX and its prior peer network-facing adapter interface is misconnected or missing.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter interface is connected to a port belonging to its peer fabric interconnect or FEX.

Step 2 If the connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: link-missing

mibFaultCode: 775

mibFaultName: fltAdaptorExtEthIfMissing

moClass: adaptor:ExtEthIf

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fltStorageLocalDiskSlotEpUnusable

Fault Code: F0776

Message

Local disk [id] on server [serverId] is not usable by the operating system

Explanation

This fault occurs when the server disk drive is in a slot that is not supported by the storage controller.

Recommended Action

If you see this fault, take the following actions:

Step 1 Insert the server disk drive in a supported slot.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-inoperable

mibFaultCode: 776

mibFaultName: fltStorageLocalDiskSlotEpUnusable

moClass: storage:LocalDiskSlotEp

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/disk-[id]

Affected MO: sys/rack-unit-[id]/board/disk-[id]

fltFabricEthEstcPcEpDown

Fault Code: F0777

Message

[type] Member [slotId]/[aggrPortId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership][type] Member [slotId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership]

Explanation

This fault typically occurs when a member port in an Ethernet port channel is down.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the link connectivity on the upstream Ethernet switch.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: membership-down

mibFaultCode: 777

mibFaultName: fltFabricEthEstcPcEpDown

moClass: fabric:EthEstcPcEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltEquipmentFexIdentity-unestablishable

Fault Code: F0778

Message

Fex [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco FPR Manager detected an unsupported chassis. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: identity-unestablishable

mibFaultCode: 778

mibFaultName: fltEquipmentFexIdentityUnestablishable

moClass: equipment:Fex

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fltEquipmentFanModuleInoperable

Fault Code: F0794

Message

Fan module [tray]-[id] in chassis [id] operability: [operability]Fan module [tray]-[id] in server [id] operability: [operability]Fan module [tray]-[id] in fabric interconnect [id] operability: [operability]

Explanation

This fault occurs if a fan module is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reinstall the fan module. If multiple fans are affected by this fault, remove and reinstall one fan module at a time.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 794

mibFaultName: fltEquipmentFanModuleInoperable

moClass: equipment:FanModule

Type: equipment

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltLsmaintMaintPolicyUnresolvableScheduler

Fault Code: F0795

Message

Schedule [schedName] referenced by maintenance policy [name] does not exist

Explanation

The schedule that is referenced by the maintenance policy does not exist. This fault typically occurs as a result of one of the following issues:

- The schedule does not exist.

- The schedule was deleted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check if the named schedule exists. If it is deleted or missing, try to create it.

Step 2 If the named schedule is deleted or missing, recreate it.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: non-existent-scheduler

mibFaultCode: 795

mibFaultName: fltLsmaintMaintPolicyUnresolvableScheduler

moClass: lsmaint:MaintPolicy

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/maint-[name]

fltProcessorUnitIdentity-unestablishable

Fault Code: F0801

Message

Processor [id] on server [chassisId]/[slotId] has an invalid FRUProcessor [id] on server [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported CPU in the server. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, you may have an unsupported CPU configuration in the server. Create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: identity-unestablishable

mibFaultCode: 801

mibFaultName: fltProcessorUnitIdentityUnestablishable

moClass: processor:Unit

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltIqnpoolPoolEmpty

Fault Code: F0821

Message

iqn pool [name] is empty

Explanation

This fault typically occurs when an IQN pool does not contain any IQNs.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the pool is in use, add a block of IQNs to the pool.

Step 2 If the pool is not in use, ignore the fault.

Fault Details

Severity: minor

Cause: empty-pool

mibFaultCode: 821

mibFaultName: fltIqnpoolPoolEmpty

moClass: iqnpool:Pool

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/iqn-pool-[name]

fltFabricDceSwSrvPcEpDown

Fault Code: F0831

Message

[type] Member [slotId]/[aggrPortId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership][type] Member [slotId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership]

Explanation

This fault typically occurs when a member port in a fabric port channel is down.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the link connectivity between the FEX or IOM and the fabric interconnect.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: membership-down

mibFaultCode: 831

mibFaultName: fltFabricDceSwSrvPcEpDown

moClass: fabric:DceSwSrvPcEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltFabricEpMgrEpTransModeFail

Fault Code: F0832

Message

Port constraint violation on switch [id]: [confQual]

Explanation

This fault occurs when at least one logical interface is misconfigured. This can happen when upgrading to a different type or series of fabric interconnect or when importing a configuration.The configuration must meet the following constraints:

- There must be at most one logical port per fabric interconnect ID/module ID/port ID.

Recommended Action

If you see this fault, take the following action:

Step 1 Create a list of all logical interfaces that are misconfigured and have caused an ’error-misconfigured’ fault.

Step 2 For each logical interface, note the reason listed in the fault for the misconfiguration.

Step 3 Log into Cisco FPR Manager and correct each misconfigured logical interface. If you used the Cisco FPR Manager CLI, commit all changes.

Step 4 Review any faults or error messages that describe additional misconfigurations and correct those errors.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: config-error

mibFaultCode: 832

mibFaultName: fltFabricEpMgrEpTransModeFail

moClass: fabric:EpMgr

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fltFabricPIoEpErrorMisconfigured

Fault Code: F0834

Message

Interface [name] is [operState]. Reason: [operStateReason]

Explanation

This fault occurs when a logical interface is misconfigured. This can happen when upgrading to a different type or series of fabric interconnect or when importing a configuration.

Recommended Action

If you see this fault, take the following action:

Step 1 Create a list of all logical interfaces that are misconfigured and have caused an ’error-misconfigured’ fault.

Step 2 For each logical interface, note the reason listed in the fault for the misconfiguration.

Step 3 Log into Cisco FPR Manager and correct each misconfigured logical interface. If you used the Cisco FPR Manager CLI, commit all changes.

Step 4 Review any faults or error messages that describe additional misconfigurations and correct those errors.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: interface-misconfigured

mibFaultCode: 834

mibFaultName: fltFabricPIoEpErrorMisconfigured

moClass: fabric:PIoEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/eth-target-ep-[name]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/phys-fc-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-group-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-group-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/san/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/san/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]

Affected MO: fabric/sanmon/[id]/fc-mon-[name]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/server/chassis-[chassisId]

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

Affected MO: fabric/server/chassis-ep-ven-[vendor]-mod[model]-ser-[serial]

Affected MO: fabric/server/compute-ep-ven-[vendor]-mod-[model]-ser-[serial]

Affected MO: fabric/server/sw-[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-port-[portId]

Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/border-eth/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/border-eth/pc-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/pc-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

fltFabricEthLanEpMissingPrimaryVlan

Fault Code: F0835

Message

Primary vlan missing from fabric: [switchId], port: [slotId]/[aggrPortId]/[portId].Primary vlan missing from fabric: [switchId], port: [slotId]/[portId].

Explanation

This fault occurs when an uplink port or port channel is configured with a primary VLAN that does not exist in the Cisco FPR instance.

Recommended Action

If you see this fault, take the following action:

Step 1 Update the configuration of the port or port channel to include a primary VLAN.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: missing-primary-vlan

mibFaultCode: 835

mibFaultName: fltFabricEthLanEpMissingPrimaryVlan

moClass: fabric:EthLanEp

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

fltFabricEthLanPcMissingPrimaryVlan

Fault Code: F0836

Message

Primary vlan missing from fabric: [switchId], port-channel: [portId].

Explanation

This fault occurs when an uplink port or port channel is configured with a primary VLAN that does not exist in the Cisco FPR instance.

Recommended Action

If you see this fault, take the following action:

Step 1 Update the configuration of the port or port channel to include a primary VLAN.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: missing-primary-vlan

mibFaultCode: 836

mibFaultName: fltFabricEthLanPcMissingPrimaryVlan

moClass: fabric:EthLanPc

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/[id]/pc-[portId]

fltVnicEtherPinningMismatch

Fault Code: F0840

Message

Hard pinning target for eth vNIC [name], service profile [name] does not have all the required vlans configured

Explanation

This fault occurs when one or more VLANs required by vNIC in a service profile are not configured on the target uplink port or port channel for a hard-pinned LAN pin group.

Recommended Action

If you see this fault, take the following actions:

Step 1 In the LAN Uplinks Manager of the Cisco FPR Manager GUI, configure all of the VLANs in the vNIC in the target uplink port or port channel for the LAN pin group. If you prefer to use the Cisco FPR Manager CLI, navigate to scope /eth-uplink/vlan and create the required member ports for the LAN pin group.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: pinning-mismatch

mibFaultCode: 840

mibFaultName: fltVnicEtherPinningMismatch

moClass: vnic:Ether

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltVnicEtherPinningMisconfig

Fault Code: F0841

Message

Hard pinning target for eth vNIC [name], service profile [name] is missing or misconfigured

Explanation

This fault occurs when one or more vNIC target uplink ports or port channels for a hard-pinned LAN pin group are either missing or misconfigured as the wrong port type.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the LAN pin group configuration.

Step 2 Correct the configuration of the port and port channels in the pin group.

Step 3 Ensure that all required vLANs are allowed on the target ports or port channels.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: pinning-misconfig

mibFaultCode: 841

mibFaultName: fltVnicEtherPinningMisconfig

moClass: vnic:Ether

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltProcessorUnitDisabled

Fault Code: F0842

Message

Processor [id] on server [chassisId]/[slotId] operState: [operState]Processor [id] on server [id] operState: [operState]

Explanation

This fault occurs in the unlikely event that a processor is disabled.

Recommended Action

If you see this fault, take the following actions:

Step 1 If this fault occurs on a blade server, remove and reinsert the server into the chassis.

Step 2 In Cisco FPR Manager, decommission and recommission the blade server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-disabled

mibFaultCode: 842

mibFaultName: fltProcessorUnitDisabled

moClass: processor:Unit

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]

Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltMemoryUnitDisabled

Fault Code: F0844

Message

DIMM [location] on server [chassisId]/[slotId] operState: [operState]DIMM [location] on server [id] operaState: [operState]

Explanation

This fault is raised when the server BIOS disables a DIMM. The BIOS could disable a DIMM for several reasons, including incorrect location of the DIMM or incompatible speed.

Recommended Action

If you see this fault, refer to the Cisco FPR B-Series Troubleshooting Guide for information on how to resolve the DIMM issues.

Fault Details

Severity: major

Cause: equipment-disabled

mibFaultCode: 844

mibFaultName: fltMemoryUnitDisabled

moClass: memory:Unit

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]

Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltFirmwareBootUnitActivateStatusFailed

Fault Code: F0856

Message

Activation failed and Activate Status set to failed.

Explanation

This fault typically occurs for the following reasons: when firmware activation fails, or if the after activation running image is not the corresponding startup image.

- Firmware activation failed.

- The version of firmware running on the server after activation is not the version listed in Cisco FPR Manager as the startup image.

Recommended Action

If you see this fault, take the following actions:

Step 1 Go to FSM tab for the endpoint on which the fault is raised and review the error description for the reason that the activation failed.

Step 2 If the FSM failed, review the error message in the FSM.

Step 3 If possible, correct the problem described in the error message.

Step 4 If the problem persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: activation-failed

mibFaultCode: 856

mibFaultName: fltFirmwareBootUnitActivateStatusFailed

moClass: firmware:BootUnit

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext/fw-boot-def/bootunit-[type]

Affected MO: capabilities/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/fpga/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/rommon/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/switch-[id]/mgmt/fw-boot-def/bootunit-[type]

fltFabricInternalPcDown

Fault Code: F0858

Message

[type] port-channel [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

Explanation

This fault occurs when the transport VIF for a server is down. Cisco FPR Manager raises this fault when a fabric interconnect reports the connectivity state on virtual interface as one of the following:

- Down

- Errored

- Unavailable

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the blade server discovery was successful.

Step 2 Check the states on all communicating ports from end to end.

Step 3 If connectivity seems correct, decommission and recommission the server.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: operational-state-down

mibFaultCode: 858

mibFaultName: fltFabricInternalPcDown

moClass: fabric:InternalPc

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/sw-[id]/pc-[portId]

fltMgmtEntityDevice-1-shared-storage-error

Fault Code: F0863

Message

device [chassis1], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action

If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: device-shared-storage-error

mibFaultCode: 863

mibFaultName: fltMgmtEntityDevice1SharedStorageError

moClass: mgmt:Entity

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityDevice-2-shared-storage error

Fault Code: F0864

Message

device [chassis2], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action

If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: device-shared-storage-error

mibFaultCode: 864

mibFaultName: fltMgmtEntityDevice2SharedStorageError

moClass: mgmt:Entity

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityDevice-3-shared-storage error

Fault Code: F0865

Message

device [chassis3], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action

If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: device-shared-storage-error

mibFaultCode: 865

mibFaultName: fltMgmtEntityDevice3SharedStorageError

moClass: mgmt:Entity

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityHa-ssh-keys-mismatched

Fault Code: F0866

Message

Fabric Interconnect [id], management services, mismatched SSH keys

Explanation

This fault indicates that one of the following scenarios has occurred:

- The internal SSH keys used for HA in the cluster configuration are mismatched. This causes certain operations to fail.

- Another fabric interconnect is connected to the primary fabric interconnect in the cluster without first erasing the existing configuration in the primary.

Recommended Action

If you see this fault, take the following actions:

Step 1 Log into the Cisco FPR Manager CLI on the subordinate fabric interconnect.

Step 2 Enter connect local-mgmt

Step 3 Enter erase configuration to erase the configuration on the subordinate fabric interconnect and reboot it.

Step 4 When the secondary fabric interconnect has rebooted, reconfigure it for the cluster.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: ha-ssh-keys-mismatched

mibFaultCode: 866

mibFaultName: fltMgmtEntityHaSshKeysMismatched

moClass: mgmt:Entity

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]

fltComputeBoardPowerFail

Fault Code: F0868

Message

Motherboard of server [chassisId]/[slotId] (service profile: [assignedToDn]) power: [power]Motherboard of server [id] (service profile: [assignedToDn]) power: [power]

Explanation

This fault typically occurs when the power sensors on a blade server detect a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove the blade server from the chassis.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: power-problem

mibFaultCode: 868

mibFaultName: fltComputeBoardPowerFail

moClass: compute:Board

Type: environmental

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/rack-unit-[id]/board

fltVmVifLinkState

Fault Code: F0876

Message

Virtual interface [vifId] link is down; reason [stateQual]

Explanation

This fault occurs when Cisco FPR cannot send or receive data through an uplink port.

Recommended Action

If you see this fault, take the following actions:

Step 1 Enable the failed uplink port.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: vif-down

mibFaultCode: 876

mibFaultName: fltVmVifLinkState

moClass: vm:Vif

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: vmm/computeEp-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]

Affected MO: vmm/hv-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]

Affected MO: vmm/vm-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]

fltEquipmentPsuPowerSupplyShutdown

Fault Code: F0881

Message

Power supply [id] in chassis [id] shutdown reason:[powerStateQualifier]

Explanation

This fault typically occurs when a power supply unit in a chassis, fabric interconnect, or a FEX is shut down, either due to higher than expected power current, higher than expected temperatures, or the failure of a fan.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Verify that the power cord is properly connected to the PSU and the power source.

Step 7 Verify that the power source is 220 volts.

Step 8 Verify that the PSU is properly installed in the chassis or fabric interconnect.

Step 9 Remove the PSU and reinstall it.

Step 10 Replace the PSU.

Step 11 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-offline

mibFaultCode: 881

mibFaultName: fltEquipmentPsuPowerSupplyShutdown

moClass: equipment:Psu

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuPowerThreshold

Fault Code: F0882

Message

Power supply [id] on chassis [id] has exceeded its power thresholdPower supply [id] on server [id] has exceeded its power threshold

Explanation

This fault occurs when a power supply unit is drawing too much current.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: power-problem

mibFaultCode: 882

mibFaultName: fltEquipmentPsuPowerThreshold

moClass: equipment:Psu

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuInputError

Fault Code: F0883

Message

Power supply [id] on chassis [id] has disconnected cable or bad input voltagePower supply [id] on server [id] has disconnected cable or bad input voltage

Explanation

This fault occurs when a power cable is disconnected or input voltage is incorrect.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: power-problem

mibFaultCode: 883

mibFaultName: fltEquipmentPsuInputError

moClass: equipment:Psu

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/psu-[id]

Affected MO: sys/fex-[id]/psu-[id]

Affected MO: sys/rack-unit-[id]/psu-[id]

Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentSwitchCardPowerOff

Fault Code: F0884

Message

Switch card is powered down.

Explanation

This fault occurs when the switch card is powered down.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: power-down

mibFaultCode: 884

mibFaultName: fltEquipmentSwitchCardPowerOff

moClass: equipment:SwitchCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/slot-[id]

fltNetworkElementInventoryFailed

Fault Code: F0885

Message

Fabric Interconnect [id] inventory is not complete [inventoryStatus]

Explanation

Cisco FPR Manager raises this fault when the management subsystem is unable to perform an inventory of the physical components, such as I/O cards or physical ports.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure that both fabric interconnects in an HA cluster are running the same software versions.

Step 2 Ensure that the fabric interconnect software is a version that is compatible with the Cisco FPR Manager software.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: inventory-failed

mibFaultCode: 885

mibFaultName: fltNetworkElementInventoryFailed

moClass: network:Element

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]

fltAdaptorUnitExtnUnidentifiable-fru

Fault Code: F0900

Message

Adapter extension [id] in server [chassisId]/[slotId] has unidentified FRU

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported adapter unit extension, such as a pass-through adaptor. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter unit extension is installed.

Step 2 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: unidentifiable-fru

mibFaultCode: 900

mibFaultName: fltAdaptorUnitExtnUnidentifiableFru

moClass: adaptor:UnitExtn

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/adaptor-extn-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/adaptor-extn-[id]

fltAdaptorUnitExtnMissing

Fault Code: F0901

Message

Adapter extension [id] in server [chassisId]/[slotId] presence: [presence]

Explanation

This fault typically occurs when an I/O adapter unit extension, such as a pass-through adapter, is missing. Cisco FPR Manager raises this fault when any of the following scenario occur:

- The endpoint reports there is no adapter unit extension, such as a pass-through adapter, plugged into the adapter slot.

- The endpoint cannot detect or communicate with the adapter unit extension plugged into the adapter slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure the adapter unit extension is properly plugged into an adapter slot in the server.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: equipment-missing

mibFaultCode: 901

mibFaultName: fltAdaptorUnitExtnMissing

moClass: adaptor:UnitExtn

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/adaptor-extn-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/adaptor-extn-[id]

fltEquipmentFexFex-unsupported

Fault Code: F0902

Message

Fex [id] with model [model] is unsupported

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported FEX. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported FEX is installed.

Step 2 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: fex-unsupported

mibFaultCode: 902

mibFaultName: fltEquipmentFexFexUnsupported

moClass: equipment:Fex

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fltVnicIScsiConfig-failed

Fault Code: F0903

Message

iSCSI vNIC [name], service profile [name] has duplicate iqn name [initiatorName]

Explanation

This fault typically occurs when IScsi Vnics refer the same iqn name.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure that iqn name unique per iSCSI vnic.

Step 2 Using show identity iqn check if the iSCSI vnic is registered in the universe.

Step 3 Try non disruptive actions such as changing description on the Service Profile to register the iqn in the universe.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: configuration-failed

mibFaultCode: 903

mibFaultName: fltVnicIScsiConfigFailed

moClass: vnic:IScsi

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/iscsi-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/iscsi-[name]

fltPkiKeyRingStatus

Fault Code: F0909

Message

[name] Keyring’s certificate is invalid, reason: [certStatus].

Explanation

This fault occurs when certificate status of Keyring has become invalid.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: invalid-keyring-certificate

mibFaultCode: 909

mibFaultName: fltPkiKeyRingStatus

moClass: pki:KeyRing

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext/keyring-[name]

fltPkiTPStatus

Fault Code: F0910

Message

[name] Trustpoint’s cert-chain is invalid, reason: [certStatus].

Explanation

This fault occurs when certificate status of TrustPoint has become invalid.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: invalid-trustpoint-cert-chain

mibFaultCode: 910

mibFaultName: fltPkiTPStatus

moClass: pki:TP

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext/tp-[name]

fltComputePhysicalDisassociationFailed

Fault Code: F0915

Message

Failed to disassociate server [id]Failed to disassociate server [chassisId]/[slotId]

Explanation

This fault typically occurs for one of the following reasons:

- The server is down.

- The data path is not working.

- Cisco FPR Manager cannot communicate with one or more of the fabric interconnect, the server, or a component on the server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the communication path to the server including fabric interconnect server ports, IOM link and the current state of the server

Step 2 If the server is stuck in an inappropriate state, such as booting, power cycle the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: disassociation-failed

mibFaultCode: 915

mibFaultName: fltComputePhysicalDisassociationFailed

moClass: compute:Physical

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltComputePhysicalNetworkMisconfigured

Fault Code: F0916

Message

Server [id] (service profile: [assignedToDn]) has mis-configured network vif resourcesServer [chassisId]/[slotId] (service profile: [assignedToDn]) has mis-configured network vif resources

Explanation

This fault would occur when FPRM VIF-id Map is not the same as the VIF-id map deployed on the adaptor upon Full Backup-Restore etc.

Recommended Action

If you see this fault, take the following actions:

Step 1 Re-acknowledge the server. This will trigger Deep Discovery-Deep Association & will resolve the issue

Step 2 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: vif-ids-mismatch

mibFaultCode: 916

mibFaultName: fltComputePhysicalNetworkMisconfigured

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltVnicProfileProfileConfigIncorrect

Fault Code: F0917

Message

The Port Profile [name] has an invalid configuration.

Explanation

This fault occurs there is an invalid entry for a port profile configuration.

Recommended Action

Check documentation and correct the offending entry in the port profile configuration.

Fault Details

Severity: warning

Cause: profile-config-incorrect

mibFaultCode: 917

mibFaultName: fltVnicProfileProfileConfigIncorrect

moClass: vnic:Profile

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles/vnic-[name]

fltVnicEtherIfVlanAccessFault

Fault Code: F0932

Message

The named vlan [name] for vNIC [name] cannot be accessed from org [name]

Explanation

This fault typically occurs when a Service Profile’s vnic interface (LAN) is resolvable but the service profile does not have access to the vlan. In this case, the default vlan will be used.

Recommended Action

This fault will be removed if you perform one of the following actions:

Step 1 Change the vnic’s interface name to a VLAN that you have access to.

Step 2 If you wish to use the default vlan, change the vnic’s interface name to default.

Step 3 Configure access to the named vlan by creating a vlan permit or vlan group permit in the service profile’s org (or a parent org).

Fault Details

Severity: major

Cause: inaccessible-vlan-referenced

mibFaultCode: 932

mibFaultName: fltVnicEtherIfVlanAccessFault

moClass: vnic:EtherIf

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]

Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]

Affected MO: fabric/lanmon/eth-flow-monitoring/flow-exporter-profile-[name]/if-[name]

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltVnicEtherIfVlanUnresolvable

Fault Code: F0933

Message

The named vlan [name] for vNIC [name] cannot be resolved

Explanation

This fault (warning) occurs when a Service Profile’s vnic interface (LAN) is unresolvable. In this case, the default vlan will be used as the operational vlan.

Recommended Action

This fault will be removed if you perform one of the following actions:

Step 1 Change the vnic interface name to an existing VLAN.

Step 2 Create the named vlan .

Fault Details

Severity: warning

Cause: referenced-vlan-unresolvable

mibFaultCode: 933

mibFaultName: fltVnicEtherIfVlanUnresolvable

moClass: vnic:EtherIf

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]

Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]

Affected MO: fabric/lanmon/eth-flow-monitoring/flow-exporter-profile-[name]/if-[name]

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltVnicEtherIfInvalidVlan

Fault Code: F0934

Message

Invalid Vlan in the allowed vlan list

Explanation

This fault typically occurs when a vnic of a service profile or a port profile contains an invalid vlan. an invalid vlan can be any one of the following:

Step 1 an isolated vlan or a community vlan that is not associated to a valid primary vlan

Step 2 a primary vlan without any of its assoicated secondary vlans allowed on the vnic

Step 3 a vlan which has sharing-type or primary vlan name not matching to that of vlan in lan-side/appliance-side

Recommended Action

This fault will be removed if you perform one of the following actions:

Step 1 if invalid vlan is an isolated or community vlan then make sure it is mapped to a valid primary vlan.

Step 2 if invalid vlan is a primary vlan then either allow any of its secondary vlans or delete it from vnic or port profile.

Step 3 if invalid vlan is a vlan that does not match the sharing properties with the vlan of same vlan id in the lan-side/appliance-side, change the properties of this vlan to be the same as the other.

Fault Details

Severity: major

Cause: invalid-vlan-in-the-allowed-vlan-list

mibFaultCode: 934

mibFaultName: fltVnicEtherIfInvalidVlan

moClass: vnic:EtherIf

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]

Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]

Affected MO: fabric/lanmon/eth-flow-monitoring/flow-exporter-profile-[name]/if-[name]

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltFabricVlanVlanConflictPermit

Fault Code: F0935

Message

There are multiple vlans with id [id] have different accessability configured.

Explanation

This fault occurs when multipl global vlans with the same id have different access configurations.

Recommended Action

Change the access configuration by configuring VLAN/VLAN Group Permits.

Fault Details

Severity: warning

Cause: vlan-conflict-permit

mibFaultCode: 935

mibFaultName: fltFabricVlanVlanConflictPermit

moClass: fabric:Vlan

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltFabricVlanReqVlanPermitUnresolved

Fault Code: F0936

Message

The VLAN permit does not reference any existing vlans.

Explanation

This fault occurs when a VLAN permit exists but there are no vnics by the name.

Recommended Action

Delete the VLAN permit, create the referenced VLAN (or ignore).

Fault Details

Severity: warning

Cause: vlan-permit-unresolved

mibFaultCode: 936

mibFaultName: fltFabricVlanReqVlanPermitUnresolved

moClass: fabric:VlanReq

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vlan-req-[name]

fltFabricVlanGroupReqVlanGroupPermitUnresolved

Fault Code: F0937

Message

The VLAN permit does not reference any existing net groups.

Explanation

This fault occurs when a VLAN group permit exists but there are no referenced network groups.

Recommended Action

Delete the VLAN permit, create the referenced VLAN (or ignore).

Fault Details

Severity: warning

Cause: group-permit-unresolved

mibFaultCode: 937

mibFaultName: fltFabricVlanGroupReqVlanGroupPermitUnresolved

moClass: fabric:VlanGroupReq

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vlan-group-req-[name]

fltExtpolClientClientLostConnectivity

Fault Code: F0988

Message

FPRM has lost connectivity with Firepower Central

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: client-lost-connectivity

mibFaultCode: 988

mibFaultName: fltExtpolClientClientLostConnectivity

moClass: extpol:Client

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltStorageLocalDiskDegraded

Fault Code: F0996

Message

Local disk [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Local disk [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the local disk has become degraded. The fault description will contain the physical drive state, which indicates the reason for the degradation.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the drive state is "rebuild" or "copyback", wait for the rebuild or copyback operation to complete.

Step 2 If the drive state is "predictive-failure", replace the disk.

Fault Details

Severity: warning

Cause: equipment-degraded

mibFaultCode: 996

mibFaultName: fltStorageLocalDiskDegraded

moClass: storage:LocalDisk

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageRaidBatteryDegraded

Fault Code: F0997

Message

RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the RAID backup unit is degraded.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault reason indicates the backup unit is in a relearning cycle, wait for relearning to complete.

Step 2 If the fault reason indicates the backup unit is about to fail, replace the backup unit.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 997

mibFaultName: fltStorageRaidBatteryDegraded

moClass: storage:RaidBattery

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageRaidBatteryRelearnAborted

Fault Code: F0998

Message

RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when the backup unit’s relearning cycle was aborted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Retry the learn cycle.

Step 2 Replace the backup unit.

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 998

mibFaultName: fltStorageRaidBatteryRelearnAborted

moClass: storage:RaidBattery

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageRaidBatteryRelearnFailed

Fault Code: F0999

Message

RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when the backup unit’s relearning cycle has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Retry the learn cycle.

Step 2 Replace the backup unit.

Fault Details

Severity: major

Cause: equipment-degraded

mibFaultCode: 999

mibFaultName: fltStorageRaidBatteryRelearnFailed

moClass: storage:RaidBattery

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageInitiatorConfiguration-error

Fault Code: F1001

Message

Initiator [name] either cannot be resolved or does not match with one of the storage targets. No zones are deployed for this initiator and the target.

Explanation

Initiator either cannot be resolved or does not match with one of the targets.

Recommended Action

If you see this fault, take the following action:

Step 1 Check if vhba interface referenced by this Initiator exsits.

Step 2 Check if switch id or vsan name of the vhba interface referenced by this Initiator matches one of the targets.

Fault Details

Severity: warning

Cause: configuration-error

mibFaultCode: 1001

mibFaultName: fltStorageInitiatorConfigurationError

moClass: storage:Initiator

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/grp-[name]/ini-[name]

Affected MO: org-[name]/san-conn-pol-[name]/grp-[name]/ini-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/grp-[name]/ini-[name]

fltStorageControllerPatrolReadFailed

Fault Code: F1003

Message

Controller [id] on server [chassisId]/[slotId] had a patrol read failure. Reason: [operQualifierReason]Controller [id] on server [id] had a patrol read failure. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when a Patrol Read operation has failed.

Recommended Action

Re-run the patrol read operation.

Fault Details

Severity: warning

Cause: operation-failed

mibFaultCode: 1003

mibFaultName: fltStorageControllerPatrolReadFailed

moClass: storage:Controller

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]

fltStorageControllerInoperable

Fault Code: F1004

Message

Controller [id] on server [chassisId]/[slotId] is inoperable. Reason: [operQualifierReason]Controller [id] on server [id] is inoperable. Reason: [operQualifierReason]

Explanation

This fault occurs when the storage controller is inaccessible.

Recommended Action

For PCI and mezz-based storage controllers, check the seating of the storage controller. If the problem persists, replace the controller.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 1004

mibFaultName: fltStorageControllerInoperable

moClass: storage:Controller

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]

fltStorageLocalDiskRebuildFailed

Fault Code: F1005

Message

Local disk [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Local disk [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when a rebuild operation has failed. This may cause a degradation in performance.

Recommended Action

If you see this fault, take the following action:

Step 1 Retry the rebuild operation.

Step 2 Replace the disk.

Fault Details

Severity: major

Cause: equipment-offline

mibFaultCode: 1005

mibFaultName: fltStorageLocalDiskRebuildFailed

moClass: storage:LocalDisk

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageLocalDiskCopybackFailed

Fault Code: F1006

Message

Local disk [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Local disk [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when a copyback operation has failed. This may cause a degradation in performance.

Recommended Action

If you see this fault, take the following action:

Step 1 Retry the copyback operation.

Step 2 Replace the disk.

Fault Details

Severity: major

Cause: equipment-offline

mibFaultCode: 1006

mibFaultName: fltStorageLocalDiskCopybackFailed

moClass: storage:LocalDisk

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageVirtualDriveInoperable

Fault Code: F1007

Message

Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the virtual drive has become inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the presence and health of disks that are used by the virtual drive.

Step 2 If applicable, reseat or replace used disks.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-inoperable

mibFaultCode: 1007

mibFaultName: fltStorageVirtualDriveInoperable

moClass: storage:VirtualDrive

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveDegraded

Fault Code: F1008

Message

Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

This fault occurs when the virtual drive has become degraded. The fault description will contain the physical drive state, which indicates the reason for the degradation.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the drive is performing a consistency check operation, wait for the operation to complete.

Step 2 Verify the presence and health of disks that are used by the virtual drive.

Step 3 If applicable, reseat or replace used disks.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-degraded

mibFaultCode: 1008

mibFaultName: fltStorageVirtualDriveDegraded

moClass: storage:VirtualDrive

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveReconstructionFailed

Fault Code: F1009

Message

Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when a drive reconstruction operation has failed. This may cause a degradation in performance.

Recommended Action

If you see this fault, take the following action:

Step 1 Retry the reconstruction operation.

Step 2 Delete and recreate the virtual drive.

Fault Details

Severity: major

Cause: equipment-degraded

mibFaultCode: 1009

mibFaultName: fltStorageVirtualDriveReconstructionFailed

moClass: storage:VirtualDrive

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveConsistencyCheckFailed

Fault Code: F1010

Message

Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation

NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.---This fault occurs when a drive consistency check operation has failed. This may cause a degradation in performance.

Recommended Action

If you see this fault, take the following action:

Step 1 Retry the consistency check operation.

Step 2 Delete and recreate the virtual drive.

Fault Details

Severity: major

Cause: equipment-degraded

mibFaultCode: 1010

mibFaultName: fltStorageVirtualDriveConsistencyCheckFailed

moClass: storage:VirtualDrive

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: false

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltAaaProviderGroupProvidergroup

Fault Code: F1026

Message

For [dn]: Server Group with name [name] already exist, You need to specify a unique name for this object.

Explanation

This fault typically occurs because Cisco FPR Manager has detected multiple provider-groups with same name.

Recommended Action

If you see this fault, take the following actions:

Step 1 Need to delete the duplicate provider group configured causing this problem.

Fault Details

Severity: major

Cause: provider-group-already-exists

mibFaultCode: 1026

mibFaultName: fltAaaProviderGroupProvidergroup

moClass: aaa:ProviderGroup

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext/providergroup-[name]

Affected MO: sys/radius-ext/providergroup-[name]

Affected MO: sys/tacacs-ext/providergroup-[name]

fltAaaConfigServergroup

Fault Code: F1027

Message

For [dn]: [realm] Server Group with name [providerGroup] doesn’t exist or is not deployed.

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported authentication method.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that server group configured for authentication is present.

Step 2 If the server group is not configured, create the server group to use for authentication.

Fault Details

Severity: critical

Cause: invalid-server-group

mibFaultCode: 1027

mibFaultName: fltAaaConfigServergroup

moClass: aaa:Config

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm/console-auth

Affected MO: sys/auth-realm/default-auth

Affected MO: sys/auth-realm/domain-[name]/domain-auth

fltAaaRoleRoleNotDeployed

Fault Code: F1028

Message

Role [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported role.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that total number of roles is less than maximum supported roles.

Step 2 Verify that sum of privileges across all roles is less than maximum privileges sum.

Fault Details

Severity: critical

Cause: role-config-error

mibFaultCode: 1028

mibFaultName: fltAaaRoleRoleNotDeployed

moClass: aaa:Role

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext/role-[name]

fltAaaLocaleLocaleNotDeployed

Fault Code: F1029

Message

Locale [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported locale.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that total number of locale is less than maximum supported roles.

Fault Details

Severity: critical

Cause: locale-config-error

mibFaultCode: 1029

mibFaultName: fltAaaLocaleLocaleNotDeployed

moClass: aaa:Locale

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext/locale-[name]

fltAaaUserRoleUserRoleNotDeployed

Fault Code: F1030

Message

For user: [name] role [name] can’t be assigned. Error: [configStatusMessage].For Ldap Group: [name] role [name] can’t be assigned. Error: [configStatusMessage].

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported user role for ldap groups or local users.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the role is present .

Step 2 Verify that the role is applied .

Step 3 Verify that the role is compatible with locales assigned to ldap group or local user .

Fault Details

Severity: critical

Cause: user-role-config-error

mibFaultCode: 1030

mibFaultName: fltAaaUserRoleUserRoleNotDeployed

moClass: aaa:UserRole

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext/ldapgroup-[name]/role-[name]

Affected MO: sys/user-ext/remoteuser-[name]/role-[name]

Affected MO: sys/user-ext/user-[name]/role-[name]

fltAaaUserLocaleUserLocaleNotDeployed

Fault Code: F1031

Message

For user: [name] locale [name] can’t be assigned. Error: [configStatusMessage].For Ldap Group: [name] locale [name] can’t be assigned. Error: [configStatusMessage].

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported user locale for ldap groups or local users.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the locale is present .

Step 2 Verify that the locale is applied .

Step 3 Verify that the locale is compatible with roles assigned to ldap group or local user .

Fault Details

Severity: critical

Cause: user-locale-config-error

mibFaultCode: 1031

mibFaultName: fltAaaUserLocaleUserLocaleNotDeployed

moClass: aaa:UserLocale

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext/ldapgroup-[name]/locale-[name]

Affected MO: sys/user-ext/remoteuser-[name]/locale-[name]

Affected MO: sys/user-ext/user-[name]/locale-[name]

fltPkiKeyRingKeyRingNotDeployed

Fault Code: F1032

Message

Keyring [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an invalid Keyring.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the trust point configured for this keyring is present .

Step 2 Verify that the trust point found above is applied .

Fault Details

Severity: critical

Cause: keyring-config-error

mibFaultCode: 1032

mibFaultName: fltPkiKeyRingKeyRingNotDeployed

moClass: pki:KeyRing

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext/keyring-[name]

fltCommSnmpSyscontactEmpty

Fault Code: F1033

Message

FPR Manager cannot deploy an empty value of SNMP Syscontact when Callhome is enabled. The previous value [sysContact] for SNMP Syscontact has been retained.

Explanation

This fault typically occurs when FPR Manager receives an invalid configuration from FPR Central wherein SNMP Syscontact is set to empty when Callhome is enabled.

Recommended Action

If you see this fault, please ensure that the SNMP Syscontact field on FPR Central is configured correctly for the domain group corresponding to this FPRM.

Fault Details

Severity: warning

Cause: snmp-config-error

mibFaultCode: 1033

mibFaultName: fltCommSnmpSyscontactEmpty

moClass: comm:Snmp

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext/snmp-svc

fltCommDateTimeCommTimeZoneInvalid

Fault Code: F1034

Message

Timezone:[timezone] is invalid

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unsupported role.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that total number of roles is less than maximum supported roles.

Step 2 Verify that sum of privileges across all roles is less than maximum privileges sum.

Fault Details

Severity: minor

Cause: timezone-file-not-exists

mibFaultCode: 1034

mibFaultName: fltCommDateTimeCommTimeZoneInvalid

moClass: comm:DateTime

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext/datetime-svc

fltAaaUserLocalUserNotDeployed

Fault Code: F1035

Message

Local User [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an invalid system user.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that local user name is not used by snmp users.

Fault Details

Severity: major

Cause: user-config-error

mibFaultCode: 1035

mibFaultName: fltAaaUserLocalUserNotDeployed

moClass: aaa:User

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext/user-[name]

fltCommSnmpUserSnmpUserNotDeployed

Fault Code: F1036

Message

SNMP User [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an invalid snmp user.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that snmp user name is not used by system users.

Fault Details

Severity: major

Cause: snmp-user-config-error

mibFaultCode: 1036

mibFaultName: fltCommSnmpUserSnmpUserNotDeployed

moClass: comm:SnmpUser

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext/snmp-svc/snmpv3-user-[name]

fltCommSvcEpCommSvcNotDeployed

Fault Code: F1037

Message

Communication Service configuration can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an invalid communication policy confiuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that ports configured across all communication services is unique.

Fault Details

Severity: major

Cause: comm-svc-config-error

mibFaultCode: 1037

mibFaultName: fltCommSvcEpCommSvcNotDeployed

moClass: comm:SvcEp

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fltSwVlanPortNsVLANCompNotSupport

Fault Code: F1056

Message

VLAN Port Count Optimization is not supported

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: no-vlan-optimization

mibFaultCode: 1056

mibFaultName: fltSwVlanPortNsVLANCompNotSupport

moClass: sw:VlanPortNs

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/vlan-port-ns

fltPolicyControlEpSuspendModeActive

Fault Code: F1057

Message

FPRM is suspended from receiving updates from FPR Central.

Explanation

This fault occurs when FPRM enters into suspend state from receiving updates from FPR Central that it is registered with.

Recommended Action

If you see this fault, take the following actions:

Step 1 Please check if FPR Central is restored to a previous version or a policy roll-back has occured. You may have brought FPR in to manual suspension mode by using set suspendstate on command under the system-control-ep policy scope.

Step 2 Please confirm the suspend state by using show control-ep policy detail under system scope. If you still want to receive the updates from FPR Central, you need to restore it back to a version compatible with FPRM or set the suspend state to off by acknowledging it by using set ackstate acked under policy-control scope.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: suspend-mode-entered

mibFaultCode: 1057

mibFaultName: fltPolicyControlEpSuspendModeActive

moClass: policy:ControlEp

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]

fltNetworkElementThermalThresholdCritical

Fault Code: F1080

Message

Fabric Interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a Fabric Interconnect exceeds a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the Fabric Interconnect.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the Fabric Interconnects have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 6 Replace faulty Fabric Interconnects.

Step 7 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 1080

mibFaultName: fltNetworkElementThermalThresholdCritical

moClass: network:Element

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]

fltFabricPinTargetDown

Fault Code: F1088

Message

Pin target is a non-existent interface

Explanation

This fault typically occurs when a PinGroup has an unresolvable target.

Recommended Action

If you see this fault, take the following action:

Step 1 Check whether the PinGroup target is correctly provisioned.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: invalid-target

mibFaultCode: 1088

mibFaultName: fltFabricPinTargetDown

moClass: fabric:PinTarget

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/lan-pin-group-[name]/target-[fabricId]

Affected MO: fabric/san/san-pin-group-[name]/target-[fabricId]

fltFabricEthLanEpOverlapping-vlan

Fault Code: F1090

Message

On Fabric: [switchId], Port: [slotId]/[aggrPortId]/[portId] following overlapping VLANs detected: [overlappingVlans]On Fabric: [switchId], Port: [slotId]/[portId] following overlapping VLANs detected: [overlappingVlans]

Explanation

This fault occurs when Overlapping Vlans occur due to mis configuration.

Recommended Action

Ports configured on Vlans belonging to a group should not intersect with other ports of different network group belonging to Vlans which overlap .

Fault Details

Severity: info

Cause: configuration-error

mibFaultCode: 1090

mibFaultName: fltFabricEthLanEpOverlappingVlan

moClass: fabric:EthLanEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

fltFabricEthLanPcOverlapping-vlan

Fault Code: F1091

Message

Overlapping VLANs detected on Fabric: [switchId], Port: [portId] in configured VLANs: [overlappingVlans]

Explanation

This fault occurs when Overlapping Vlans occur due to mis configuration.

Recommended Action

Ports configured on Vlans belonging to a group should not intersect with other ports of different network group belonging to Vlans which overlap .

Fault Details

Severity: info

Cause: configuration-error

mibFaultCode: 1091

mibFaultName: fltFabricEthLanPcOverlappingVlan

moClass: fabric:EthLanPc

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/[id]/pc-[portId]

fltFabricVlanMisconfigured-mcast-policy

Fault Code: F1095

Message

VLAN [name] multicast policy [mcastPolicyName] is non-default.

Explanation

This fault is raised when VLAN belonging to a Springfield fabric has a non-default multicast policy assigned to it.

Recommended Action

If you see this fault, take the following action:

Step 1 Un-assign multicast policy for the this vlan or change the multicast policy to default.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: vlan-mcast-policy-misconfigured

mibFaultCode: 1095

mibFaultName: fltFabricVlanMisconfiguredMcastPolicy

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltMgmtConnectionDisabled

Fault Code: F1097

Message

Management Connection [type] in server [id] is not operational

Explanation

This fault occurs when multiple management connections are acknowledegd.

Recommended Action

If you see this fault, take the following actions:

Step 1 Disable the management connection which is unused.

Step 2 If new management connection needs to be used, decommission and recommission server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: another-connection-already-enabled

mibFaultCode: 1097

mibFaultName: fltMgmtConnectionDisabled

moClass: mgmt:Connection

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltMgmtConnectionUnused

Fault Code: F1098

Message

Management Connection [type] in server [id] is unused

Explanation

This fault occurs when a management connection is not enabel

Recommended Action

If you see this fault, you can enable the connection if none of the management connections are enabled. Else this can be ignored

Fault Details

Severity: info

Cause: connection-unused

mibFaultCode: 1098

mibFaultName: fltMgmtConnectionUnused

moClass: mgmt:Connection

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltMgmtConnectionUnsupportedConnectivity

Fault Code: F1099

Message

Unsupported connectivity for management connection [type] in server [id]

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the physical connectivity of the management port of the server is unsupported.

Recommended Action

If you see this fault, take the following actions:

Step 1 Connect the management port/s of the rack mount server to the Fabric Extender/s

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: unsupported-connectivity

mibFaultCode: 1099

mibFaultName: fltMgmtConnectionUnsupportedConnectivity

moClass: mgmt:Connection

Type: operational

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]

Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltCallhomeEpNoSnmpPolicyForCallhome

Fault Code: F1102

Message

FPR Manager cannot apply Callhome policy if SNMP Policy is not configured or if SNMP Syscontact has an empty value. The Callhome policy from FPR Central has not been applied.

Explanation

This fault typically occurs when FPR Manager receives an invalid configuration from FPR Central wherein Callhome is configured on FPR Central but there is no SNMP Syscontact defined locally.

Recommended Action

If you see this fault, please ensure that the SNMP Policy is configured on FPRM Manager, either locally or via FPR Central.

Fault Details

Severity: minor

Cause: callhome-config-error

mibFaultCode: 1102

mibFaultName: fltCallhomeEpNoSnmpPolicyForCallhome

moClass: callhome:Ep

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fltCapabilityCatalogueLoadErrors

Fault Code: F1103

Message

Load errors: File parse errors: [fileParseFailures], provider load failures: [providerLoadFailures], XML element load errors: [loadErrors].

Explanation

The capability catalog failed to load fully. This may be caused by either a faulty FPRM image or a faulty catalog image.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the version of the capability catalog.

Step 2 Contact Cisco TAC to see if there are known issues with the catalog and if there is a catalog image that will fix the known issues.

Fault Details

Severity: major

Cause: load-catalog-failed

mibFaultCode: 1103

mibFaultName: fltCapabilityCatalogueLoadErrors

moClass: capability:Catalogue

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fltExtmgmtArpTargetsArpTargetsNotValid

Fault Code: F1114

Message

Invalid ARP Targets configured for Management Interface Polling. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an invalid ArpTargets Configuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that Arp target ip address and external management ip address are in the same subnet.

Step 2 Verify that Arp target ip address is not the same as ip address of this system’s fabric-interconnects.

Step 3 Verify that Arp target ip address is not the same as virtual IP Address.

Fault Details

Severity: major

Cause: arp-targets-config-error

mibFaultCode: 1114

mibFaultName: fltExtmgmtArpTargetsArpTargetsNotValid

moClass: extmgmt:ArpTargets

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extmgmt-intf-monitor-policy/arp-target-policy

fltExtpolClientGracePeriodWarning

Fault Code: F1211

Message

FPR domain [name] registered with FPR Central has entered into the grace period.

Explanation

A FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under license scope from service-reg session.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: license-graceperiod-entered

mibFaultCode: 1211

mibFaultName: fltExtpolClientGracePeriodWarning

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning2

Fault Code: F1212

Message

FPR Domain [name] registered with FPR Central is running in the grace period for more than 10 days

Explanation

This FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: license-graceperiod-10days

mibFaultCode: 1212

mibFaultName: fltExtpolClientGracePeriodWarning2

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning3

Fault Code: F1213

Message

FPR Domain [name] registered with FPR Central is running in the grace period for more than 30 days

Explanation

This FPR Domain registered with FPR Central has been running in the grace period for more than 30 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 120 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Manager GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: license-graceperiod-30days

mibFaultCode: 1213

mibFaultName: fltExtpolClientGracePeriodWarning3

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning4

Fault Code: F1214

Message

FPR Domain [name] registered with FPR Central is running in the grace period for more than 60 days

Explanation

This FPR Domain registered with FPR Central has been running in the grace period for more than 60 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 60 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: license-graceperiod-60days

mibFaultCode: 1214

mibFaultName: fltExtpolClientGracePeriodWarning4

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning5

Fault Code: F1215

Message

FPR Domain [name] registered with FPR Central is running in the grace period for more than 90 days

Explanation

This FPR Domain registered with FPR Central has been running in the grace period for more than 90 days. This fault typically occurs if this FPR domains is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 90 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed by FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: license-graceperiod-90days

mibFaultCode: 1215

mibFaultName: fltExtpolClientGracePeriodWarning5

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning6

Fault Code: F1216

Message

FPR Domain [name] registered with FPR Central is running in the grace period for more than 119 days

Explanation

This FPR Domain registered with FPR Central has been running in the grace period for more than 119 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 119 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: license-graceperiod-119days

mibFaultCode: 1216

mibFaultName: fltExtpolClientGracePeriodWarning6

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning7

Fault Code: F1217

Message

Grace period for FPR Domain [name] registered with FPR Central has expired. Please acquire a license for the same.

Explanation

This FPR Domain registered with FPR Central has been running in the grace period for more than 120 days. FPR domains are registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 120 days. At this stage, the system licensing state is set to expired.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed FPR Domains to bring the number of enabled Domains down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical

Cause: license-graceperiod-expired

mibFaultCode: 1217

mibFaultName: fltExtpolClientGracePeriodWarning7

moClass: extpol:Client

Type: management

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning1

Fault Code: F1218

Message

FPR Domain [name] is registered with FPR Central without a valid license.

Explanation

This FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central without the initial activation license and after all default licenses are assigned to other FPR domains.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check if the initial activation license is installed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed FPR Domains to bring the number of enabled Domains down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical

Cause: license-insufficient

mibFaultCode: 1218

mibFaultName: fltExtpolClientGracePeriodWarning1

moClass: extpol:Client

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]

fltStorageItemFilesystemIssues

Fault Code: F1219

Message

Partition [name] on fabric interconnect [id] has file system errors

Explanation

This fault occurs when the partition develops faults

Recommended Action

If you see this fault, take the following actions:

Step 1 Create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: equipment-degraded

mibFaultCode: 1219

mibFaultName: fltStorageItemFilesystemIssues

moClass: storage:Item

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/stor-part-[name]

fltPkiKeyRingModulus

Fault Code: F1222

Message

[name] Keyring’s key modulus is invalid.

Explanation

This fault occurs when keyring is created without modulus set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: invalid-keyring-modulus

mibFaultCode: 1222

mibFaultName: fltPkiKeyRingModulus

moClass: pki:KeyRing

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext/keyring-[name]

fltAaaOrgLocaleOrgNotPresent

Fault Code: F1223

Message

Locale Org [name] can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco FPR Manager has detected an unidentified org reference.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the org dn referenced in this Org is exists, if not create the same.

Fault Details

Severity: warning

Cause: locale-org-config-error

mibFaultCode: 1223

mibFaultName: fltAaaOrgLocaleOrgNotPresent

moClass: aaa:Org

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext/locale-[name]/org-[name]

fltNetworkOperLevelExtraprimaryvlans

Fault Code: F1229

Message

Fabric Interconnect [id]: Number of primary vlans exceeds the max limit on the FI: Number of Primary Vlans: [primaryVlanCount] and Max primary vlans allowed: [maxPrimaryVlanCount]

Explanation

This fault occurs when the fabric interconnect has more number of primary vlans than what is supported.

Recommended Action

If you see this fault, take the following actions:

Step 1 It is recommended that operator should delete the extra primary vlans than are there in the FI. System may appear to be normally functioning even with these extra primary vlans in place. However there may be performance issues observed as the system is operating above the recommended scale limits..

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: extra-primary-vlans

mibFaultCode: 1229

mibFaultName: fltNetworkOperLevelExtraprimaryvlans

moClass: network:OperLevel

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/oper-level

fltEquipmentHealthLedCriticalError

Fault Code: F1236

Message

Health LED of server [chassisId]/[slotId] shows error. Reason: [healthLedStateQualifier]Health LED of server [id] shows error. Reason: [healthLedStateQualifier]

Explanation

This fault is raised Blade LED changes to amber blinking

Recommended Action

If you see this fault, take the following actions:

Step 1 Read fault summary and determine course of action.

Fault Details

Severity: critical

Cause: health-led-amber-blinking

mibFaultCode: 1236

mibFaultName: fltEquipmentHealthLedCriticalError

moClass: equipment:HealthLed

Type: equipment

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/health-led

Affected MO: sys/chassis-[id]/blade-[slotId]/health-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/chassis-[id]/health-led

Affected MO: sys/chassis-[id]/psu-[id]/health-led

Affected MO: sys/chassis-[id]/slot-[id]/health-led

Affected MO: sys/fex-[id]/health-led

Affected MO: sys/fex-[id]/psu-[id]/health-led

Affected MO: sys/fex-[id]/slot-[id]/health-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/health-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/rack-unit-[id]/health-led

Affected MO: sys/rack-unit-[id]/psu-[id]/health-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/switch-[id]/psu-[id]/health-led

fltEquipmentHealthLedMinorError

Fault Code: F1237

Message

Health LED of server [chassisId]/[slotId] shows error. Reason: [healthLedStateQualifier]Health LED of server [id] shows error. Reason: [healthLedStateQualifier]

Explanation

This fault is raised Blade LED changes to amber

Recommended Action

If you see this fault, take the following actions:

Step 1 Read fault summary and determine course of action.

Fault Details

Severity: minor

Cause: health-led-amber

mibFaultCode: 1237

mibFaultName: fltEquipmentHealthLedMinorError

moClass: equipment:HealthLed

Type: equipment

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/health-led

Affected MO: sys/chassis-[id]/blade-[slotId]/health-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/chassis-[id]/health-led

Affected MO: sys/chassis-[id]/psu-[id]/health-led

Affected MO: sys/chassis-[id]/slot-[id]/health-led

Affected MO: sys/fex-[id]/health-led

Affected MO: sys/fex-[id]/psu-[id]/health-led

Affected MO: sys/fex-[id]/slot-[id]/health-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/health-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/rack-unit-[id]/health-led

Affected MO: sys/rack-unit-[id]/psu-[id]/health-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/health-led

Affected MO: sys/switch-[id]/psu-[id]/health-led

fltVnicEtherIfRemoteVlanUnresolvable

Fault Code: F1249

Message

The named vlan [name] for vNIC [name] cannot be resolved remotely

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: referenced-remote-vlan-unresolvable

mibFaultCode: 1249

mibFaultName: fltVnicEtherIfRemoteVlanUnresolvable

moClass: vnic:EtherIf

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]

Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]

Affected MO: fabric/lanmon/eth-flow-monitoring/flow-exporter-profile-[name]/if-[name]

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltVnicEtherVirtualization-conflict

Fault Code: F1251

Message

Multiple connection policies cannot be assigned to the same Eth vNIC

Explanation

This fault occurs when multiple connection policies are assigned to the same vNIC.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check on the vNIC if different types of connection policies (dynamic/VMQ) are assigned. Keep only one type.

Step 2 Check on the vNIC through CLI if more than one connection policy of the same type is assigned. Keep only one connection policy.

Fault Details

Severity: major

Cause: multiple-connection-policies

mibFaultCode: 1251

mibFaultName: fltVnicEtherVirtualizationConflict

moClass: vnic:Ether

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltLsIssuesIscsi-config-failed

Fault Code: F1252

Message

Service Profile [name] configuration failed due to iSCSI issue [iscsiConfigIssues]

Explanation

This fault typically occurs when Cisco FPR Manager Service Profile configuration failed due to iSCSI Config Issues.

Recommended Action

If you see this fault, take the following actions:

Step 1 Correct the Service Profile iSCSI Configuration as per the issue reported.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: configuration-failed

mibFaultCode: 1252

mibFaultName: fltLsIssuesIscsiConfigFailed

moClass: ls:Issues

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/config-issue

Affected MO: org-[name]/tier-[name]/ls-[name]/config-issue

fltStorageLocalDiskMissing

Fault Code: F1256

Message

Local disk [id] missing on server [chassisId]/[slotId]Local disk [id] missing on server [id]

Explanation

This fault occurs when a disk is missing.

Recommended Action

If you see this fault, take the following action:

Step 1 Insert the disk.

Fault Details

Severity: info

Cause: equipment-missing

mibFaultCode: 1256

mibFaultName: fltStorageLocalDiskMissing

moClass: storage:LocalDisk

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageFlexFlashControllerInoperable

Fault Code: F1257

Message

FlexFlash Controller [id] on server [chassisId]/[slotId] is inoperable. Reason: [operQualifierReason] Status: [controllerHealth]FlexFlash Controller [id] on server [id] is inoperable. Reason: [operQualifierReason] Status: [controllerHealth]

Explanation

This fault occurs when the flexflash controller is inaccessible.

Recommended Action

If you see this fault, take the following action:

Step 1 If reported as Firmware Mismatch, update the CIMC and Board Controller firmware

Step 2 If reported as Fatal Error, reset the CIMC and update Board Controller firmware

Step 3 For PCI and mezz-based controllers, check the seating of the storage controller. If the problem persists, replace the controller

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 1257

mibFaultName: fltStorageFlexFlashControllerInoperable

moClass: storage:FlexFlashController

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fltStorageFlexFlashCardInoperable

Fault Code: F1258

Message

FlexFlash Card [slotNumber] on server [chassisId]/[slotId] is inoperable. Reason: [operQualifierReason]FlexFlash Card [slotNumber] on server [id] is inoperable. Reason: [operQualifierReason]

Explanation

This fault occurs when the flexflash card is inaccessible.

Recommended Action

If you see this fault, take the following action:

Step 1 If reported as Write Protected, then remove write protection from the card

Step 2 If reported as Invalid Capacity, use an OS disk utility to delete/recreate the partitions

Step 3 If the above action did not resolve the issue, replace the card

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 1258

mibFaultName: fltStorageFlexFlashCardInoperable

moClass: storage:FlexFlashCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/card-[slotNumber]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/card-[slotNumber]

fltStorageFlexFlashCardMissing

Fault Code: F1259

Message

FlexFlash Card [slotNumber] missing on server [chassisId]/[slotId]FlexFlash Card [slotNumber] missing on server [id]

Explanation

This fault occurs when a FlexFlash Card is missing.

Recommended Action

If you see this fault, take the following action:

Step 1 Insert the Card.

Fault Details

Severity: info

Cause: equipment-missing

mibFaultCode: 1259

mibFaultName: fltStorageFlexFlashCardMissing

moClass: storage:FlexFlashCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/card-[slotNumber]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/card-[slotNumber]

fltStorageFlexFlashVirtualDriveDegraded

Fault Code: F1260

Message

FlexFlash Virtual Drive RAID degraded on server [chassisId]/[slotId]. Reason: [raidState]FlexFlash Virtual Drive RAID degraded on server [id]. Reason: [raidState]

Explanation

This fault occurs when the flexflash raid is degraded.

Recommended Action

If you see this fault, take the following action:

Step 1 Re-acknowledge the server by setting the flexflash scrub policy to yes. Please note that this action will erase all data in the card(s)

Step 2 Verify the health of the controller/card(s). If the above action did not resolve the issue, replace the card(s)

Fault Details

Severity: minor

Cause: equipment-degraded

mibFaultCode: 1260

mibFaultName: fltStorageFlexFlashVirtualDriveDegraded

moClass: storage:FlexFlashVirtualDrive

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/vd-[id]

fltStorageFlexFlashVirtualDriveInoperable

Fault Code: F1261

Message

FlexFlash Virtual Drive on server [chassisId]/[slotId] is inoperable. Reason: [raidState]FlexFlash Virtual Drive on server [id] is inoperable. Reason: [raidState]

Explanation

This fault occurs when the flexflash virtual drive is inoperable.

Recommended Action

If you see this fault, take the following action:

Step 1 Re-acknowledge the server by setting the flexflash scrub policy to yes. Please note that this action will erase all data in the card(s)

Step 2 Verify the health of the controller/card(s). If the above action did not resolve the issue, replace the card(s)

Fault Details

Severity: major

Cause: equipment-inoperable

mibFaultCode: 1261

mibFaultName: fltStorageFlexFlashVirtualDriveInoperable

moClass: storage:FlexFlashVirtualDrive

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/vd-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/vd-[id]

fltStorageFlexFlashControllerUnhealthy

Fault Code: F1262

Message

FlexFlash Controller [id] on server [chassisId]/[slotId] is unhealthy. Reason: [operQualifierReason] Status: [controllerHealth]FlexFlash Controller [id] on server [id] is unhealthy. Reason: [operQualifierReason] Status: [controllerHealth]

Explanation

This fault occurs when the flexflash controller is unhealthy.

Recommended Action

If you see this fault, take the following action:

Step 1 If reported as Old Firmware/Firmware Mismatch, update the CIMC and Board Controller firmware, reboot the server

Step 2 Re-acknowledge the server by setting the flexflash scrub policy to yes. Please note that this action will erase all data in the card(s)

Step 3 Verify the health of the controller. If the above action did not resolve the issue, replace the card(s)

Fault Details

Severity: minor

Cause: equipment-unhealthy

mibFaultCode: 1262

mibFaultName: fltStorageFlexFlashControllerUnhealthy

moClass: storage:FlexFlashController

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fltAaaProviderGroupProvidergroupsize

Fault Code: F1279

Message

For [dn]: Server Group [name] has [size] provider references. Authentication might fail, if this provider group is used with auth-domain.

Explanation

This fault typically occurs because Cisco FPR Manager has detected provider-group with 0 provider references..

Recommended Action

If you see this fault, take the following actions:

Step 1 Need to delete the provider group which does not have any provider references.

Step 2 Or Add provider references to provider group.

Fault Details

Severity: warning

Cause: provider-group-size-empty

mibFaultCode: 1279

mibFaultName: fltAaaProviderGroupProvidergroupsize

moClass: aaa:ProviderGroup

Type: security

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext/providergroup-[name]

Affected MO: sys/radius-ext/providergroup-[name]

Affected MO: sys/tacacs-ext/providergroup-[name]

fltFirmwareAutoSyncPolicyDefaultHostPackageMissing

Fault Code: F1284

Message

Default host firmware package is missing or deleted.

Explanation

This fault typically occurs for the following reasons: when Auto Firmware Sync Policy is set Auto-acknowledge or User-acknowledge and default host firmware pack is not available.

- Auto Firmware Sync is not happening.

- Default host firmware package is missing or deleted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Go to Servers tab and expand policies node. Select Host Firmware Packages under policies node.

Step 2 If the FSM failed, review the error message in the FSM.

Step 3 Create a host firmware package with name ’default’. If the problem persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: default-hostpack-missing

mibFaultCode: 1284

mibFaultName: fltFirmwareAutoSyncPolicyDefaultHostPackageMissing

moClass: firmware:AutoSyncPolicy

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-auto-sync

fltFabricNetflowMonSessionFlowMonConfigFail

Fault Code: F1304

Message

Configuration for traffic flow monitor [name] failed, reason: [configFailReason]

Explanation

This fault typically occurs when the configuration of a traffic flow monitoring session is incorrect.

Recommended Action

If you see this fault, correct the configuration problem provided in the fault description.

Fault Details

Severity: major

Cause: config-error

mibFaultCode: 1304

mibFaultName: fltFabricNetflowMonSessionFlowMonConfigFail

moClass: fabric:NetflowMonSession

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lanmon/eth-flow-monitoring/netflow-mon-[name]

fltFabricNetflowMonSessionNetflowSessionConfigFail

Fault Code: F1305

Message

Netflow session configuration failed because [configQualifier]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: config-error

mibFaultCode: 1305

mibFaultName: fltFabricNetflowMonSessionNetflowSessionConfigFail

moClass: fabric:NetflowMonSession

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lanmon/eth-flow-monitoring/netflow-mon-[name]

fltFabricPooledVlanNamedVlanUnresolved

Fault Code: F1306

Message

VLAN [name] for VLAN group [name] cannot be resolved to any existing vlans.

Explanation

This fault typically occurs when a named VLAN in VLAN group cannot be resolved to any existing vlans.

Recommended Action

If you see this fault, take the following action:

Step 1 Create VLAN.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: named-vlan-unresolved

mibFaultCode: 1306

mibFaultName: fltFabricPooledVlanNamedVlanUnresolved

moClass: fabric:PooledVlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/[id]/net-group-[name]/net-[name]

Affected MO: fabric/lan/net-group-[name]/net-[name]

fltExtvmmVMNDRefVmNetworkReferenceIncorrect

Fault Code: F1320

Message

VM Network [name] references [vmNetworkDefName] that is already being referenced by another VM Network

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: vm-network-reference-incorrect

mibFaultCode: 1320

mibFaultName: fltExtvmmVMNDRefVmNetworkReferenceIncorrect

moClass: extvmm:VMNDRef

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/vm-network-sets/vm-network-[name]/vm-network-def-ref[name]

fltExtmgmtNdiscTargetsNdiscTargetsNotValid

Fault Code: F1321

Message

Invalid NDISC Targets configured for Management Interface Polling. Error: [configStatusMessage]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: ndisc-targets-config-error

mibFaultCode: 1321

mibFaultName: fltExtmgmtNdiscTargetsNdiscTargetsNotValid

moClass: extmgmt:NdiscTargets

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extmgmt-intf-monitor-policy/ndisc-target-policy

fltFirmwareBootUnitPowerCycleRequired

Fault Code: F1325

Message

Board controller upgraded, manual a/c power cycle required on server [serverId]

Explanation

None set.

Recommended Action

If you see this fault, take the following actions:

Step 1 Power cycle the board controller.

Fault Details

Severity: critical

Cause: board-ctrl-upgraded

mibFaultCode: 1325

mibFaultName: fltFirmwareBootUnitPowerCycleRequired

moClass: firmware:BootUnit

Type: generic

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext/fw-boot-def/bootunit-[type]

Affected MO: capabilities/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/fpga/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/rommon/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/mgmt/fw-boot-def/bootunit-[type]

Affected MO: sys/rack-unit-[id]/os-ctrl/fw-boot-def/bootunit-[type]

Affected MO: sys/switch-[id]/mgmt/fw-boot-def/bootunit-[type]

fltMgmtControllerUnsupportedDimmBlacklisting

Fault Code: F1328

Message

Dimm blacklisting is not supported on server [chassisId]/[slotId]Dimm blacklisting is not supported on server [id]

Explanation

This fault typically occurs when the CIMC firmware on a server is an earlier release than Cisco FPR, Release 2.2.

Recommended Action

If you see this fault, consider upgrading the CIMC firmware, and the entire Cisco FPR instance if necessary, to Cisco FPR, Release 2.2 or later.

Fault Details

Severity: info

Cause: incompatible-server-firmware

mibFaultCode: 1328

mibFaultName: fltMgmtControllerUnsupportedDimmBlacklisting

moClass: mgmt:Controller

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fltFabricEthLanEpUdldLinkDown

Fault Code: F1358

Message

UDLD state for ether port [slotId]/[aggrPortId]/[portId] on fabric interconnect [switchId] is: [udldOperState].UDLD state for ether port [slotId]/[portId] on fabric interconnect [switchId] is: [udldOperState].

Explanation

This fault occurs when an ethernet uplink port is unidirectional connected.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the tx and rx connection of the uplink port.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: udld-link-down

mibFaultCode: 1358

mibFaultName: fltFabricEthLanEpUdldLinkDown

moClass: fabric:EthLanEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

fltFabricEthLanPcEpUdldLinkDown

Fault Code: F1359

Message

UDLD state for ether port [slotId]/[aggrPortId]/[portId] on fabric interconnect [switchId] is: [udldOperState].UDLD state for ether port [slotId]/[portId] on fabric interconnect [switchId] is: [udldOperState].

Explanation

This fault occurs when an ethernet uplink port-channel member is unidirectional connected.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the tx and rx connection of the uplink port.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: udld-link-down

mibFaultCode: 1359

mibFaultName: fltFabricEthLanPcEpUdldLinkDown

moClass: fabric:EthLanPcEp

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/fc-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltEquipmentChassisInvalid-fru

Fault Code: F1407

Message

Chassis [id] has a empty value for FRU identity reported by CMC.

Explanation

This fault typically occurs when the FRU information for a chassis has empty value.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 1407

mibFaultName: fltEquipmentChassisInvalidFru

moClass: equipment:Chassis

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fltEquipmentSwitchIOCardRemoved

Fault Code: F1408

Message

[side] FI IOM [chassisId]/[id] ([switchId]) is removed

Explanation

This fault typically occurs because an FI I/O module is removed from the chassis. In a cluster configuration, the chassis fails over to the other FI I/O module. For a standalone configuration, the chassis associated with the FI I/O module loses network connectivity. This is a critical fault because it can result in the loss of network connectivity and disrupt data traffic through the FI I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reinsert the FI I/O module and configure the fabric-interconnect ports connected to it as server ports and wait a few minutes to see if the fault clears.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-removed

mibFaultCode: 1408

mibFaultName: fltEquipmentSwitchIOCardRemoved

moClass: equipment:SwitchIOCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardThermalProblem

Fault Code: F1409

Message

[side] FI IOM [chassisId]/[id] ([switchId]) operState: [operState]

Explanation

This fault occurs when there is a thermal problem on an FI I/O module. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the FI I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the FI I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty FI I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 1409

mibFaultName: fltEquipmentSwitchIOCardThermalProblem

moClass: equipment:SwitchIOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardThermalThresholdNonCritical

Fault Code: F1410

Message

[side] FI IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an FI I/O module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the FI I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and FI I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and FI I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: thermal-problem

mibFaultCode: 1410

mibFaultName: fltEquipmentSwitchIOCardThermalThresholdNonCritical

moClass: equipment:SwitchIOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardThermalThresholdCritical

Fault Code: F1411

Message

[side] FI IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an FI I/O module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the FI I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and FI I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and FI I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty FI I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 1411

mibFaultName: fltEquipmentSwitchIOCardThermalThresholdCritical

moClass: equipment:SwitchIOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardThermalThresholdNonRecoverable

Fault Code: F1412

Message

[side] FI IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an FI I/O module has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

- Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

- Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

- If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the FI I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and FI I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and FI I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty FI I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 1412

mibFaultName: fltEquipmentSwitchIOCardThermalThresholdNonRecoverable

moClass: equipment:SwitchIOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardIdentity

Fault Code: F1414

Message

[side] FI IOM [chassisId]/[id] ([switchId]) has a malformed FRU

Explanation

This fault typically occurs when the FRU information for an FI I/O module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco FPR Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fru-problem

mibFaultCode: 1414

mibFaultName: fltEquipmentSwitchIOCardIdentity

moClass: equipment:SwitchIOCard

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltEquipmentSwitchIOCardCpuThermalThresholdCritical

Fault Code: F1415

Message

[side] FI IOM [chassisId]/[id] ([switchId]) processor temperature exceeded the limit

Explanation

This fault typically occurs when the processor temperature in FI-IOM exceeds the limit.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the FI I/O module.

Step 2 Review the Cisco FPR Site Preparation Guide to ensure the chassis and FI I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco FPR chassis and FI I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty FI I/O modules.

Step 8 Use the Cisco FPR power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system’s maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: thermal-problem

mibFaultCode: 1415

mibFaultName: fltEquipmentSwitchIOCardCpuThermalThresholdCritical

moClass: equipment:SwitchIOCard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/sw-slot-[id]

fltPowerBudgetChassisPsuMixedMode

Fault Code: F1421

Message

Chassis [id] has a mix of high-line and low-line PSU input power sources.

Explanation

This fault occurs when there is a mix of high-line and low-line PSU input power source.

Recommended Action

If you see this fault, change all the PSU input power sources to have same mode

Fault Details

Severity: critical

Cause: psu-mixed-mode

mibFaultCode: 1421

mibFaultName: fltPowerBudgetChassisPsuMixedMode

moClass: power:Budget

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/budget

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget

Affected MO: sys/chassis-[id]/budget

Affected MO: sys/rack-unit-[id]/budget

Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltNetworkElementRemoved

Fault Code: F1426

Message

Fabric Interconnect [id] operability: [operability]

Explanation

This fault occurs when the fabric interconnect is removed in a clustering setup.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reinsert the removed fabric interconnect back into the chassis (applicable to FPR-Mini only).

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: equipment-removed

mibFaultCode: 1426

mibFaultName: fltNetworkElementRemoved

moClass: network:Element

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]

fltNetworkOperLevelExtrasecondaryvlans

Fault Code: F1432

Message

Fabric Interconnect [id]: Number of secondary vlans exceeds the max limit on the FI: Number of secondary vlans: [secondaryVlanCount] and Max secondary vlans allowed: [maxSecondaryVlanCount]

Explanation

This fault occurs when the fabric interconnect has more number of secondary vlans than what is supported.

Recommended Action

If you see this fault, take the following actions:

Step 1 It is recommended that operator should delete the extra secondary vlans that are there in the FI. System may appear to be normally functioning even with these extra secondary vlans in place. However there may be performance issues observed as the system is operating above the recommended scale limits..

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: extra-secondary-vlans

mibFaultCode: 1432

mibFaultName: fltNetworkOperLevelExtrasecondaryvlans

moClass: network:OperLevel

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/oper-level

fltSwVlanExtrasecondaryvlansperprimary

Fault Code: F1433

Message

Number of secondary vlans associated with the primary vlan [id] in Fabric Interconnect [switchId] exceeds the max limit: Number of secondary vlans: [secVlanPerPrimaryVlanCount] and Max secondary vlans allowed in a primary vlan: 30

Explanation

This fault occurs when the fabric interconnect has more number of secondary vlans per primary vlan than what is supported.

Recommended Action

If you see this fault, take the following actions:

Step 1 It is recommended that operator should delete the extra secondary vlans on this primary vlan that are there in the FI. System may appear to be normally functioning even with these extra secondary vlans on this primary vlan in place. However there may be performance issues observed as the system is operating above the recommended scale limits..

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: extra-secondary-vlans-per-primary

mibFaultCode: 1433

mibFaultName: fltSwVlanExtrasecondaryvlansperprimary

moClass: sw:Vlan

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles/vnic-[name]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/pc-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-eth/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/fcoesan-pc-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/border-fc/vlan-[id]

Affected MO: sys/switch-[id]/ethlanflowmon/flowexporter-netflow-[name]/vlan-[id]

Affected MO: sys/switch-[id]/ethlanflowmon/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/pc-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vlan-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]/fcoesan-pc-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]/vc-[id]/vlan-[id]

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoeestc-ep-slot-[slotId]port-[portId]/vlan-[id]

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesan-ep-slot-[slotId]port-[portId]/vlan-[id]

fltMgmtBackupPolicyConfigConfiguration backup outdated

Fault Code: F1437

Message

Config backup may be outdated

Explanation

This fault occurs when last backup configuration is taken long back

Recommended Action

If you see this fault, take the following actions:

Step 1 Please take a configuration backup

Fault Details

Severity: minor

Cause: config-backup-outdated

mibFaultCode: 1437

mibFaultName: fltMgmtBackupPolicyConfigConfigurationBackupOutdated

moClass: mgmt:BackupPolicyConfig

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/bkup-policy-cfg

fltFirmwareStatusCimcFirmwareMismatch

Fault Code: F1441

Message

Aggregate blade CIMC firmware mismatch. Firmware: [cimcVersion]

Explanation

This fault typically occurs when the CIMC firmware image on master and slave node in an aggregate blade does not match.

Recommended Action

Update and activate master and slave CIMC to same firmware version.

Fault Details

Severity: critical

Cause: cimc-firmware-mismatch

mibFaultCode: 1441

mibFaultName: fltFirmwareStatusCimcFirmwareMismatch

moClass: firmware:Status

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/fw-status

Affected MO: sys/chassis-[id]/slot-[id]/fw-status

Affected MO: sys/fex-[id]/slot-[id]/fw-status

Affected MO: sys/fw-status

Affected MO: sys/rack-unit-[id]/fw-status

Affected MO: sys/switch-[id]/fw-status

fltFirmwareStatusPldFirmwareMismatch

Fault Code: F1442

Message

Aggregate blade board controller firmware mismatch. Firmware: [pldVersion]

Explanation

This fault typically occurs when the board controller firmware image on master and slave node in an aggregate blade does not match.

Recommended Action

Update master and slave board controller to same firmware version.

Fault Details

Severity: critical

Cause: pld-firmware-mismatch

mibFaultCode: 1442

mibFaultName: fltFirmwareStatusPldFirmwareMismatch

moClass: firmware:Status

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/fw-status

Affected MO: sys/chassis-[id]/slot-[id]/fw-status

Affected MO: sys/fex-[id]/slot-[id]/fw-status

Affected MO: sys/fw-status

Affected MO: sys/rack-unit-[id]/fw-status

Affected MO: sys/switch-[id]/fw-status

fltVnicEtherVirtualization-netflow-conflict

Fault Code: F1443

Message

Netflow and VMQ/SRIOV-USNIC policies cannot be assigned to the same Eth vNIC

Explanation

This fault typically occurs when a netflow src vnic is made a USNIC or VMQ vnic

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove the vnic from a netflow session or remove the usnic/vmq policy

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: multiple-connection-policies

mibFaultCode: 1443

mibFaultName: fltVnicEtherVirtualizationNetflowConflict

moClass: vnic:Ether

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]

Affected MO: org-[name]/ls-[name]/ether-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltSysdebugLogExportStatusLogExportFailure

Fault Code: F1444

Message

Log export to remote server failed from [switchId]:[exportFailureReason]

Explanation

This fault occurs when Cisco Firepower Manager cannot transfer a log file to a remote server. This is typically the result of one of the following issues:

- The remote server is not accessible.

- One or more of the parameters for the remote server that are specified for the log export target, such as path, username, password, ssh-key and server name, are incorrect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the connectivity to the remote server.

Step 2 Verify the path information of the remote server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: server-error

mibFaultCode: 1444

mibFaultName: fltSysdebugLogExportStatusLogExportFailure

moClass: sysdebug:LogExportStatus

Type: sysdebug

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy/log-export-status-[switchId]

fltLsServerSvnicNotPresent

Fault Code: F1459

Message

Service profile [name] does not contain service vnics for netflow.

Explanation

The service profile does not have service vnics, hence netflow will not function on this server. This fault typically occurs as a result of one of the following issues:

- Service profile has maximum number of vnics already created, hence cannot accomodate service vnics required for netflow.

Recommended Action

If you see this fault, take the following actions:

Step 1 If you have already enabled netflow, please reduce the number of vnics on the SP to accomodate service vnics.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning

Cause: svnic-not-present

mibFaultCode: 1459

mibFaultName: fltLsServerSvnicNotPresent

moClass: ls:Server

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fltLsIssuesKvmPolicyUnsupported

Fault Code: F1460

Message

Kvm mgmt policy not supported by current CIMC version

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: unsupported-cimc-firmware

mibFaultCode: 1460

mibFaultName: fltLsIssuesKvmPolicyUnsupported

moClass: ls:Issues

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/config-issue

Affected MO: org-[name]/tier-[name]/ls-[name]/config-issue

fltComputeABoardThermalProblem

Fault Code: F1461

Message

Motherboard [faultQualifier] of server [chassisId]/[slotId] (service profile: [assignedToDn]) thermal: [thermal]Motherboard of server [id] (service profile: [assignedToDn]) thermal: [thermal]

Explanation

This fault typically occurs when the motherboard thermal sensors on a server detect a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server fans are working properly.

Step 2 Wait for 24 hours to see if the problem resolves itself.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: thermal-problem

mibFaultCode: 1461

mibFaultName: fltComputeABoardThermalProblem

moClass: compute:ABoard

Type: environmental

Callhome: environmental

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltComputeABoardPowerUsageProblem

Fault Code: F1462

Message

Motherboard [faultQualifier] of server [chassisId]/[slotId] (service profile: [assignedToDn]) powerUsage: [powerUsage]Motherboard of server [id] (service profile: [assignedToDn]) powerUsage: [powerUsage]

Explanation

This fault typically occurs when the motherboard power consumption exceeds certain threshold limits. At that time the power usage sensors on a server detect a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: power-problem

mibFaultCode: 1462

mibFaultName: fltComputeABoardPowerUsageProblem

moClass: compute:ABoard

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltComputeABoardMotherBoardVoltageThresholdUpperNonRecoverable

Fault Code: F1463

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has become too high and is unlikely to recover.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 1463

mibFaultName: fltComputeABoardMotherBoardVoltageThresholdUpperNonRecoverable

moClass: compute:ABoard

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltComputeABoardMotherBoardVoltageThresholdLowerNonRecoverable

Fault Code: F1464

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has dropped too low and is unlikely to recover.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: voltage-problem

mibFaultCode: 1464

mibFaultName: fltComputeABoardMotherBoardVoltageThresholdLowerNonRecoverable

moClass: compute:ABoard

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltComputeABoardMotherBoardVoltageUpperThresholdCritical

Fault Code: F1465

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has crossed upper critical thresholds.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: voltage-problem

mibFaultCode: 1465

mibFaultName: fltComputeABoardMotherBoardVoltageUpperThresholdCritical

moClass: compute:ABoard

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltComputeABoardMotherBoardVoltageLowerThresholdCritical

Fault Code: F1466

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has crossed lower critical thresholds.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: voltage-problem

mibFaultCode: 1466

mibFaultName: fltComputeABoardMotherBoardVoltageLowerThresholdCritical

moClass: compute:ABoard

Type: environmental

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]

Affected MO: sys/rack-unit-[id]/board

Affected MO: sys/rack-unit-[id]/ext-board-[id]

fltCimcvmediaActualMountEntryVmediaMountFailed

Fault Code: F1467

Message

Server [chassisId]/[slotId] (service profile: [assignedToDn]) vmedia mapping [mappingName] has failed.Server [id] (service profile: [assignedToDn]) vmedia mapping [mappingName] has failed.

Explanation

None set.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the mount related details(remote server ip, port, path & file is reachable) and reack the server .

Fault Details

Severity: major

Cause: vmedia-mount-inaccessible

mibFaultCode: 1467

mibFaultName: fltCimcvmediaActualMountEntryVmediaMountFailed

moClass: cimcvmedia:ActualMountEntry

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/fex-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/rack-unit-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

Affected MO: sys/switch-[id]/mgmt/actual-mount-list/actual-mount-entry-[virtualDiskId]

fltFabricVlanPrimaryVlanMissingForIsolated

Fault Code: F1468

Message

Primary Vlan can not be resolved for isolated vlan [name]

Explanation

This fault typically occurs when Cisco FPR Manager encounters a problem resolving the primary VLAN ID corresponding to a particular isolated VLAN.

Recommended Action

If you see this fault, take the following actions:

Step 1 Associate the isolated VLAN with a valid primary VLAN.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: primary-vlan-missing-for-isolated

mibFaultCode: 1468

mibFaultName: fltFabricVlanPrimaryVlanMissingForIsolated

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltFabricVlanPrimaryVlanMissingForCommunity

Fault Code: F1469

Message

Primary Vlan can not be resolved for community vlan [name]

Explanation

This fault typically occurs when Cisco FPR Manager encounters a problem resolving the primary VLAN ID corresponding to a particular community VLAN.

Recommended Action

If you see this fault, take the following actions:

Step 1 Associate the community VLAN with a valid primary VLAN.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor

Cause: primary-vlan-missing-for-community

mibFaultCode: 1469

mibFaultName: fltFabricVlanPrimaryVlanMissingForCommunity

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltFabricVlanMismatch-a

Fault Code: F1470

Message

VLAN [name] has [overlapStateForA] with another vlan under lan-cloud/appliance-cloud for the fabric interconnect A

Explanation

This fault typically occurs when private vlan properties of VLAN under one cloud conflicts with the private vlan properties of VLAN under another cloud for the fabric interconnect A. The cloud here means either a LAN cloud or an appliance cloud. This issue can stop the usage of this vlan.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the sharing property of the VLAN under both clouds and fabric A referred by its VLAN ID.

Step 2 If the sharing property of the VLAN does not match with the VLAN on the other cloud, then change the sharing property of either of the VLANs, so that it matches with each other.

Step 3 If the VLAN is a isolated/community vlan, check the pubnwname property of the VLAN under both clouds referred by its VLAN ID.

Step 4 If the pubnwname property of the isolated/community VLAN does not match with the isolated/community VLAN on the other cloud, then change the pubnwname property of either of the VLANs, so that it matches with each other.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: vlan-mismatch

mibFaultCode: 1470

mibFaultName: fltFabricVlanMismatchA

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltFabricVlanMismatch-b

Fault Code: F1471

Message

VLAN [name] has [overlapStateForB] with another vlan under lan-cloud/appliance-cloud for the fabric interconnect B

Explanation

This fault typically occurs when private vlan properties of VLAN under one cloud conflicts with the private vlan properties of VLAN under another cloud for the fabric interconnect B. The cloud here means either a LAN cloud or an appliance cloud. This issue can stop the usage of this vlan.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the sharing property of the VLAN under both clouds and fabric B referred by its VLAN ID.

Step 2 If the sharing property of the VLAN does not match with the VLAN on the other cloud, then change the sharing property of either of the VLANs, so that it matches with each other.

Step 3 If the VLAN is a isolated/community vlan, check the pubnwname property of the VLAN under both clouds referred by its VLAN ID.

Step 4 If the pubnwname property of the isolated/community VLAN does not match with the isolated/community VLAN on the other cloud, then change the pubnwname property of either of the VLANs, so that it matches with each other.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: vlan-mismatch

mibFaultCode: 1471

mibFaultName: fltFabricVlanMismatchB

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltFabricVlanErrorAssocPrimary

Fault Code: F1472

Message

VLAN [name] is in error state because the associated primary vlan [assocPrimaryVlanState]

Explanation

This fault typically occurs when there is an error in associated primary vlan of a secondary VLAN. This issue can stop the usage of this vlan.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the pubnwname property of the VLAN.

Step 2 If the pubnwname is not given or refers to a non-existing primary vlan, give a name of a primary vlan which is in good state.

Step 3 If the pubnwname refers to a vlan which is not a primary vlan, then either change the referred vlan to be a primary vlan or give a different primary vlan.

Step 4 If the pubnwname refers to a valid primary vlan, then check the state of the primary VLAN.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: vlan-error-assoc-primary

mibFaultCode: 1472

mibFaultName: fltFabricVlanErrorAssocPrimary

moClass: fabric:Vlan

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/eth-estc/[id]/net-[name]

Affected MO: fabric/eth-estc/net-[name]

Affected MO: fabric/lan/[id]/net-[name]

Affected MO: fabric/lan/net-[name]

fltStorageMezzFlashLifeConfiguration-error

Fault Code: F1494

Message

Flash Life on server [chassisId]/[slotId] flashStatus: [flashStatus]

Explanation

This fault occurs when FPRM is not able to retrieve the Fusion-io life left due to an error.

Recommended Action

If you see this fault, take the following actions:

Step 1 Upgrade Fusion-io Firmware.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info

Cause: configuration-error

mibFaultCode: 1494

mibFaultName: fltStorageMezzFlashLifeConfigurationError

moClass: storage:MezzFlashLife

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/flash-life-

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/flash-life-

fltStorageMezzFlashLifeDegraded

Fault Code: F1495

Message

Flash Life on server [chassisId]/[slotId] flashStatus: [flashStatus]

Explanation

This fault occurs when the Fusion-io life left is 10 percent or less.

Recommended Action

If you see this fault, take the following actions:

Step 1 Continue to monitor the the Fusion-io life left and if it reaches 0 percent, the adapter might revert to read-only.

Fault Details

Severity: warning

Cause: equipment-degraded

mibFaultCode: 1495

mibFaultName: fltStorageMezzFlashLifeDegraded

moClass: storage:MezzFlashLife

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/flash-life-

Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/flash-life-

fltStorageFlexFlashControllerMismatch

Fault Code: F1496

Message

FlexFlash Controller [id] on server [chassisId]/[slotId] has SD cards with different sizes.FlexFlash Controller [id] on server [id] has SD cards with different sizes.

Explanation

This fault occurs when the flexflash SD Cards dont match in size.

Recommended Action

If you see this fault, take the following action:

Step 1 Remove one of the existing cards and replace it with another card that has the same size as the unremoved one.

Fault Details

Severity: major

Cause: equipment-unhealthy

mibFaultCode: 1496

mibFaultName: fltStorageFlexFlashControllerMismatch

moClass: storage:FlexFlashController

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fltStorageFlexFlashDriveUnhealthy

Fault Code: F1497

Message

FlexFlash Drive [id] on server [chassisId]/[slotId] is unhealthy. Reason: [operQualifierReason] Status: [operationState]FlexFlash Drive [id] on server [id] is unhealthy. Reason: [operQualifierReason] Status: [operationState]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: equipment-unhealthy

mibFaultCode: 1497

mibFaultName: fltStorageFlexFlashDriveUnhealthy

moClass: storage:FlexFlashDrive

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/card-[slotNumber]/drive-[name]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/card-[slotNumber]/drive-[name]

fltStorageFlexFlashCardUnhealthy

Fault Code: F1498

Message

FlexFlash Card [slotNumber] on server [chassisId]/[slotId] is unhealthy. Reason: [cardHealth]FlexFlash Card [slotNumber] on server [id] is unhealthy. Reason: [cardHealth]

Explanation

This fault occurs when the flexflash card is unhealthy.

Recommended Action

If you see this fault, take the following action:

Step 1 Re-acknowledge the server by setting the flexflash scrub policy to yes. Please note that this action will erase all data in the card(s)

Step 2 Verify the health of the card. If the above action did not resolve the issue, replace the card

Fault Details

Severity: minor

Cause: equipment-unhealthy

mibFaultCode: 1498

mibFaultName: fltStorageFlexFlashCardUnhealthy

moClass: storage:FlexFlashCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]/card-[slotNumber]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]/card-[slotNumber]

fltMgmtInterfaceNamedInbandVlanUnresolved

Fault Code: F1506

Message

[configMessage]

Explanation

This fault occurs if there is an issue in Inband interface configuration.

Recommended Action

If you see this fault check if the VLAN configured on Inband IP is created and the VLAN is present in the Inband Profile or IP address is configured

Fault Details

Severity: minor

Cause: named-inband-vlan-unresolved

mibFaultCode: 1506

mibFaultName: fltMgmtInterfaceNamedInbandVlanUnresolved

moClass: mgmt:Interface

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/iface-[mode]

Affected MO: org-[name]/tier-[name]/ls-[name]/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/mgmt/iface-[mode]

Affected MO: sys/switch-[id]/mgmt/iface-[mode]

fltMgmtInterfaceInbandUnsupportedServer

Fault Code: F1507

Message

[configMessage]

Explanation

This fault occurs if there is an issue in Inband interface configuration.

Recommended Action

If you see this fault check if the VLAN configured on Inband IP is created and the VLAN is present in the Inband Profile or IP address is configured

Fault Details

Severity: minor

Cause: inband-unsupported-server

mibFaultCode: 1507

mibFaultName: fltMgmtInterfaceInbandUnsupportedServer

moClass: mgmt:Interface

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/iface-[mode]

Affected MO: org-[name]/tier-[name]/ls-[name]/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/mgmt/iface-[mode]

Affected MO: sys/switch-[id]/mgmt/iface-[mode]

fltMgmtInterfaceInbandUnsupportedFirmware

Fault Code: F1508

Message

[configMessage]

Explanation

This fault occurs if there is an issue in Inband interface configuration.

Recommended Action

If you see this fault check if the VLAN configured on Inband IP is created and the VLAN is present in the Inband Profile or IP address is configured

Fault Details

Severity: minor

Cause: unsupported-cimc-firmware

mibFaultCode: 1508

mibFaultName: fltMgmtInterfaceInbandUnsupportedFirmware

moClass: mgmt:Interface

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]/iface-[mode]

Affected MO: org-[name]/tier-[name]/ls-[name]/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/mgmt/iface-[mode]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/iface-[mode]

Affected MO: sys/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/iface-[mode]

Affected MO: sys/rack-unit-[id]/mgmt/iface-[mode]

Affected MO: sys/switch-[id]/mgmt/iface-[mode]

fltComputePhysicalAdapterMismatch

Fault Code: F1509

Message

Server [id] (service profile: [assignedToDn]) has invalid adapter combinatonServer [chassisId]/[slotId] (service profile: [assignedToDn]) has invalid adapter combination

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the server has an invalid combination of Cisco VICs.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the valid adapter combinations are installed configuration.

Step 2 Reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: adaptor-mismatch

mibFaultCode: 1509

mibFaultName: fltComputePhysicalAdapterMismatch

moClass: compute:Physical

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fltEquipmentSwitchCardAct2LiteFail

Fault Code: F1510

Message

Failed Identification Test in slot - [id] ([descr]). The module in this slot may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco modules into a Cisco productvis the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.

Explanation

This fault occurs when the ACT2 chip fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: act2-fail

mibFaultCode: 1510

mibFaultName: fltEquipmentSwitchCardAct2LiteFail

moClass: equipment:SwitchCard

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/slot-[id]

fltEquipmentTpmSlaveTpm

Fault Code: F1511

Message

Server [chassisId]/[slotId], has a Tpm present on the Slave Board.

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: info

Cause: tpm-on-slave-board

mibFaultCode: 1511

mibFaultName: fltEquipmentTpmSlaveTpm

moClass: equipment:Tpm

Type: equipment

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/Tpm-[id]

Affected MO: sys/rack-unit-[id]/board/Tpm-[id]

fltPoolElementDuplicatedAssigned

Fault Code: F1512

Message

ID is duplicated assigned for multiple servers(Check FPRC for details)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: duplicated-assigned

mibFaultCode: 1512

mibFaultName: fltPoolElementDuplicatedAssigned

moClass: pool:Element

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: ip/[id]

Affected MO: iqn/[name]

Affected MO: mac/[id]

Affected MO: uuid/[id]

Affected MO: wwn/[id]

fltSwVlanPortNsResourceStatusWarning

Fault Code: F1519

Message

Total Available Vlan-Port Count on switch [switchId] is below 10%

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: near-max-limit

mibFaultCode: 1519

mibFaultName: fltSwVlanPortNsResourceStatusWarning

moClass: sw:VlanPortNs

Type: management

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/vlan-port-ns

fltNetworkElementMemoryerror

Fault Code: F1520

Message

Fabric Interconnect [id] memory less than expected! Total Memory: [totalMemory] and Expected Memory: [expectedMemory]

Explanation

This fault occurs when the total memory on FI is less than expected.

Recommended Action

If you see this fault, take the following actions:

Step 1 You will need to do a manual physical inspection of the DIMMs on the FI. Try removing and reinserting the DIMMs, and verify the Total Memory. If this does not resolve the issue, one of the DIMMs has gone bad and needs to be replaced.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major

Cause: memory-error

mibFaultCode: 1520

mibFaultName: fltNetworkElementMemoryerror

moClass: network:Element

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]

fltMgmtPmonEntryFPRM process failure

Fault Code: F1541

Message

FPRM process [name] failed on FI [switchId]

Explanation

This fault occurs in an unlikely event of a Cisco FPR Manager process crash. Typically, the failed process restarts and recovers from the problem. Any pending operations are restarted after the process successfully restarts.

Recommended Action

If you see this fault and the process does not restart successfully, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical

Cause: fprm-process-failure

mibFaultCode: 1541

mibFaultName: fltMgmtPmonEntryFPRMProcessFailure

moClass: mgmt:PmonEntry

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/mgmt-entity-[id]/[name]

fltSmSlotSmaHeartbeat

Fault Code: F1545

Message

Slot [slotId] is not operationally up

Explanation

This fault occurs when a slot is not operationally up.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reboot the Blade associated with the Slot

Fault Details

Severity: major

Cause: slot-not-responding

mibFaultCode: 1545

mibFaultName: fltSmSlotSmaHeartbeat

moClass: sm:Slot

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]

fltSmSlotBladeNotWorking

Fault Code: F1546

Message

Slot [slotId] has a fault, either blade discovery is failed or service profile association is failed

Explanation

This fault occurs when a blade discovery is failed or service profile association is failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reboot the blade associated with the slot

Fault Details

Severity: major

Cause: blade-not-working

mibFaultCode: 1546

mibFaultName: fltSmSlotBladeNotWorking

moClass: sm:Slot

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]

fltSmSlotDiskFormatFailed

Fault Code: F1547

Message

Disk format is failed on slot [slotId]

Explanation

This fault occurs when a blade disk formatting is failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reformat disk or need disk replacement

Fault Details

Severity: major

Cause: disk-format-failed

mibFaultCode: 1547

mibFaultName: fltSmSlotDiskFormatFailed

moClass: sm:Slot

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]

fltSmSlotBladeSwap

Fault Code: F1548

Message

Blade swap detected on slot [slotId]

Explanation

This fault occurs during the blade swap.

Recommended Action

If you see this fault, take the following action:

Step 1 1. Insert the correct blade

Step 2 2. Reformat the disk

Fault Details

Severity: critical

Cause: blade-swap

mibFaultCode: 1548

mibFaultName: fltSmSlotBladeSwap

moClass: sm:Slot

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]

fltSmAppInstanceAppNotResponding

Fault Code: F1549

Message

App Instance [appName] on slot [slotId] is not responding

Explanation

This fault occurs when an app instance is not responding.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-not-responding

mibFaultCode: 1549

mibFaultName: fltSmAppInstanceAppNotResponding

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmAppInstanceAppInstallFailed

Fault Code: F1550

Message

Failed to install App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance installation fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-install-failed

mibFaultCode: 1550

mibFaultName: fltSmAppInstanceAppInstallFailed

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmAppInstanceAppStartFailed

Fault Code: F1551

Message

Failed to start App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance start fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-start-failed

mibFaultCode: 1551

mibFaultName: fltSmAppInstanceAppStartFailed

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmAppInstanceAppUpdateFailed

Fault Code: F1552

Message

Failed to update App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance updation fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-update-failed

mibFaultCode: 1552

mibFaultName: fltSmAppInstanceAppUpdateFailed

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmAppInstanceAppStopFailed

Fault Code: F1553

Message

Failed to stop App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance stop fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-stop-failed

mibFaultCode: 1553

mibFaultName: fltSmAppInstanceAppStopFailed

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltOsControllerFailedBladeBootup

Fault Code: F1568

Message

Slot [slotId], boot up failed - recovery in progress

Explanation

This fault occurs when blade failed to boot up.

Recommended Action

If you see this fault, do nothing because the blade will try to recover

Step 1 Reboot the Blade associated with the Slot

Fault Details

Severity: major

Cause: bootup-failure

mibFaultCode: 1568

mibFaultName: fltOsControllerFailedBladeBootup

moClass: os:Controller

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fltOsControllerFailedBootupRecovery

Fault Code: F1569

Message

Slot [slotId], boot up failed - exceeded max number of retries

Explanation

This fault occurs when blade failed to boot up.

Recommended Action

If you see this fault, do the following:

Step 1 Reboot the Blade associated with the Slot

Fault Details

Severity: major

Cause: bootup-failure

mibFaultCode: 1569

mibFaultName: fltOsControllerFailedBootupRecovery

moClass: os:Controller

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fltFirmwarePlatformPackBundleVersionMissing

Fault Code: F1595

Message

Platform version is empty in platform firmware package

Explanation

This fault typically occurs when the platform version is not set.

Recommended Action

If you see this fault, take the following actions:

Step 1 In the CLI, under scope org/fw-platform-pack, set the platform-bundle-vers to a desired or expected running platform version.

Fault Details

Severity: critical

Cause: default-plaform-version-missing

mibFaultCode: 1595

mibFaultName: fltFirmwarePlatformPackBundleVersionMissing

moClass: firmware:PlatformPack

Type: management

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fltSmSecSvcSwitchConfigFail

Fault Code: F1626

Message

Switch configuration failed for Logical Device. Error: [switchErrorMsg]

Explanation

This fault occurs when switch configuration fails for a LogicalDevice.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: switch-config-failed

mibFaultCode: 1626

mibFaultName: fltSmSecSvcSwitchConfigFail

moClass: sm:SecSvc

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc

fltSmAppInstanceAppInstanceError

Fault Code: F1627

Message

Error in App Instance [appName]. [errorMsg]

Explanation

This fault occurs when an app instance is in a non-terminal error state.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: appinstance-error

mibFaultCode: 1627

mibFaultName: fltSmAppInstanceAppInstanceError

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmLogicalDeviceIncompleteConfig

Fault Code: F1628

Message

Logical Device [name] is not configured correctly. Error [errorMsg]

Explanation

This fault occurs when a logical device is not configured correctly.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: logical-device-incomplete-configuration

mibFaultCode: 1628

mibFaultName: fltSmLogicalDeviceIncompleteConfig

moClass: sm:LogicalDevice

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fltSmLogicalDeviceLogicalDeviceError

Fault Code: F1629

Message

Error in Logical Device [name]. [errorMsg]

Explanation

This fault occurs when a logical device is in a non-terminal error state.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: logical-device-error

mibFaultCode: 1629

mibFaultName: fltSmLogicalDeviceLogicalDeviceError

moClass: sm:LogicalDevice

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fltSmAppLicenseAgreementNotAccepted

Fault Code: F1630

Message

End User License Agreement not accepted for Application [name].[version]

Explanation

This fault occurs when an application requiring End User License Agreement(EULA) is downloaded but EULA is yet to be accepted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Accept the license aggrement for this application

Fault Details

Severity: major

Cause: license-agreement-not-accepted

mibFaultCode: 1630

mibFaultName: fltSmAppLicenseAgreementNotAccepted

moClass: sm:App

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fltSmAppInstanceAppInstanceUnsupported

Fault Code: F1631

Message

App Instance [appName] on slot [slotId] is not supported in the current bundle. Error: [errorMsg]

Explanation

This fault occurs when an app instance is not supported in the current platform bundle

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: appinstance-unsupported

mibFaultCode: 1631

mibFaultName: fltSmAppInstanceAppInstanceUnsupported

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltSmAppInstanceSoftwareIncompatible

Fault Code: F1633

Message

[versionIncompatibleErrorMgr]

Explanation

This fault occurs when this main app version is not compatible with decorator version or this decorator version is not compatible with main app version.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove data port decorator from logical device

Fault Details

Severity: major

Cause: software-version-incompatible

mibFaultCode: 1633

mibFaultName: fltSmAppInstanceSoftwareIncompatible

moClass: sm:AppInstance

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fltEtherFtwPortPairBypass

Fault Code: F1638

Message

Port-pair [portName]-[peerPortName] in hardware-bypass mode

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: bypass

mibFaultCode: 1638

mibFaultName: fltEtherFtwPortPairBypass

moClass: ether:FtwPortPair

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/fail-to-wire/ftw-port-[slotId]-[aggrPortId]-[portId]-port-[peerSlotId]-[peerAggrPortId]-[peerPortId]

fltCommDateTimeCommNtpConfigurationFailed

Fault Code: F1661

Message

Ntp Configuration failed, please check the error message in Ntp host

Explanation

This fault typically occurs because all Ntp configuration failed adn the system is out of sync.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that whether at least one Ntp configuration succeeded.

Fault Details

Severity: major

Cause: ntp-config-failed

mibFaultCode: 1661

mibFaultName: fltCommDateTimeCommNtpConfigurationFailed

moClass: comm:DateTime

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext/datetime-svc

fltSmConfigIssueLogicalDeviceConfigError

Fault Code: F1671

Message

[errorMsg]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: logical-device-config-error

mibFaultCode: 1671

mibFaultName: fltSmConfigIssueLogicalDeviceConfigError

moClass: sm:ConfigIssue

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]/config-issue-[moKey]

fltSmAppAppImageCorrupted

Fault Code: F1673

Message

The application image [appId] is corrupted

Explanation

This fault occurs when an application meta data cannot be reloaded.

Recommended Action

If you see this fault, take the following actions:

Step 1 Re-download the application from a trusted source

Fault Details

Severity: major

Cause: app-img-corrupted

mibFaultCode: 1673

mibFaultName: fltSmAppAppImageCorrupted

moClass: sm:App

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fltEquipmentXcvrNonSupportedXcvr

Fault Code: F1677

Message

The transceiver inserted in port Ethernet [slotId]/[aggrPortId]/[portId] is not a Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco modules into a Cisco product is the cause of a support issue, Cisco TAC reserves the right to deny support

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: fru-problem

mibFaultCode: 1677

mibFaultName: fltEquipmentXcvrNonSupportedXcvr

moClass: equipment:Xcvr

Type: equipment

Callhome: diagnostic

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]/transceiver

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/transceiver

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]/transceiver

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/transceiver

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]/transceiver

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/transceiver

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]/transceiver

Affected MO: sys/rack-unit-[id]/diag/port-[portId]/transceiver

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/transceiver

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]/transceiver

fltFabricSspEthMonDelAllSessEnabled

Fault Code: F1679

Message

Packet Capture Session [name] was still enabled when delete-all-sessions was issued

Explanation

This fault occurs when user issues the delete-all-sessions command when one of the packet capture sessions is still enabled

Recommended Action

If you see this fault, take the following actions:

Step 1 Disable the enabled session

Step 2 Retry the delete-all-sessions command

Fault Details

Severity: warning

Cause: config-error

mibFaultCode: 1679

mibFaultName: fltFabricSspEthMonDelAllSessEnabled

moClass: fabric:SspEthMon

Type: network

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/ssppktcapmon/ssp-mon-[name]

fltIpsecConnectionIpsecConnInvalidKey

Fault Code: F1681

Message

Invalid keyring [keyring] for IPSec connection [name]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: ipsec-config-error

mibFaultCode: 1681

mibFaultName: fltIpsecConnectionIpsecConnInvalidKey

moClass: ipsec:Connection

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext/conn-[name]

fltIpsecConnectionIpsecConnInvalidCert

Fault Code: F1682

Message

Invalid Cert of keyring [keyring] for IPSec connection [name]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: ipsec-config-error

mibFaultCode: 1682

mibFaultName: fltIpsecConnectionIpsecConnInvalidCert

moClass: ipsec:Connection

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext/conn-[name]

fltIpsecAuthorityIpsecAuthorInvalidTp

Fault Code: F1683

Message

Invalid trustpoint [tpName] for IPSec

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: ipsec-config-error

mibFaultCode: 1683

mibFaultName: fltIpsecAuthorityIpsecAuthorInvalidTp

moClass: ipsec:Authority

Type: configuration

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext/author-[tpName]

fltSmHotfixHotfixInstallFailed

Fault Code: F1691

Message

Failed to install Hotfix [version] on [appName] in slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when hotfix installation fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: hotfix-install-failed

mibFaultCode: 1691

mibFaultName: fltSmHotfixHotfixInstallFailed

moClass: sm:Hotfix

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]/hotfix-[version]

fltSmHotfixHotfixError

Fault Code: F1692

Message

Error in Hotfix [version] on appInstance [appName] in slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when hotfix is in a non-terminal error state.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: minor

Cause: hotfix-error

mibFaultCode: 1692

mibFaultName: fltSmHotfixHotfixError

moClass: sm:Hotfix

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]/hotfix-[version]

fltSmErrorError

Fault Code: F1693

Message

[operStr] failed on slot [slotId]:[errorMsg]

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: generic-error

mibFaultCode: 1693

mibFaultName: fltSmErrorError

moClass: sm:Error

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]/error-[moKey]

fltSmCloudConnectorCloudRegistrationFailed

Fault Code: F1694

Message

Failed to register the device with the cloud. Error: [errorMessage]

Explanation

This fault occurs when registration of device with cloud fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: cloud-registration-failed

mibFaultCode: 1694

mibFaultName: fltSmCloudConnectorCloudRegistrationFailed

moClass: sm:CloudConnector

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fltSmCloudConnectorCloudUnregistrationFailed

Fault Code: F1695

Message

Failed to unregister the device with the cloud. Error: [errorMessage]

Explanation

This fault occurs when unregistration of device with cloud fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: major

Cause: cloud-unregistration-failed

mibFaultCode: 1695

mibFaultName: fltSmCloudConnectorCloudUnregistrationFailed

moClass: sm:CloudConnector

Type: server

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

FSM Faults

This chapter provides information about the faults that may be raised during one or more stages of an FSM task.

Note Unless an FSM fault appears on the Overview page, you do not need to take any action to resolve the fault. FSM stages fail and retry for many reasons. These faults do not always indicate an issue with a component or the FSM.

fsmStFailEquipmentChassisRemoveChassis:DisableEndPoint

Fault Code: F16407

Message

[FSM:STAGE:FAILED|RETRY]: unconfiguring access to chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:DisableEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-end-point-failed

mibFaultCode: 16407

mibFaultName: fsmStFailEquipmentChassisRemoveChassisDisableEndPoint

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRemoveChassis:UnIdentifyLocal

Fault Code: F16407

Message

[FSM:STAGE:FAILED|RETRY]: erasing chassis identity [id] from primary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-local-failed

mibFaultCode: 16407

mibFaultName: fsmStFailEquipmentChassisRemoveChassisUnIdentifyLocal

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRemoveChassis:UnIdentifyPeer

Fault Code: F16407

Message

[FSM:STAGE:FAILED|RETRY]: erasing chassis identity [id] from secondary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-peer-failed

mibFaultCode: 16407

mibFaultName: fsmStFailEquipmentChassisRemoveChassisUnIdentifyPeer

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRemoveChassis:Wait

Fault Code: F16407

Message

[FSM:STAGE:FAILED|RETRY]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 16407

mibFaultName: fsmStFailEquipmentChassisRemoveChassisWait

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRemoveChassis:decomission

Fault Code: F16407

Message

[FSM:STAGE:FAILED|RETRY]: decomissioning chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:decomission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: decomission-failed

mibFaultCode: 16407

mibFaultName: fsmStFailEquipmentChassisRemoveChassisDecomission

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentLocatorLedSetLocatorLed:Execute

Fault Code: F16408

Message

[FSM:STAGE:FAILED|RETRY]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16408

mibFaultName: fsmStFailEquipmentLocatorLedSetLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmStFailMgmtControllerExtMgmtIfConfig:Primary

Fault Code: F16518

Message

[FSM:STAGE:FAILED|RETRY]: external mgmt interface configuration on primary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Primary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: primary-failed

mibFaultCode: 16518

mibFaultName: fsmStFailMgmtControllerExtMgmtIfConfigPrimary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerExtMgmtIfConfig:Secondary

Fault Code: F16518

Message

[FSM:STAGE:FAILED|RETRY]: external mgmt interface configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Secondary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: secondary-failed

mibFaultCode: 16518

mibFaultName: fsmStFailMgmtControllerExtMgmtIfConfigSecondary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailFabricComputeSlotEpIdentify:ExecuteLocal

Fault Code: F16519

Message

[FSM:STAGE:FAILED|RETRY]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 16519

mibFaultName: fsmStFailFabricComputeSlotEpIdentifyExecuteLocal

moClass: fabric:ComputeSlotEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fsmStFailFabricComputeSlotEpIdentify:ExecutePeer

Fault Code: F16519

Message

[FSM:STAGE:FAILED|RETRY]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 16519

mibFaultName: fsmStFailFabricComputeSlotEpIdentifyExecutePeer

moClass: fabric:ComputeSlotEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fsmStFailComputeBladeDiscover:BiosPostCompletion

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBiosPostCompletion

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BladeBootPnuos

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: power server [chassisId]/[slotId] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-pnuos-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBladeBootPnuos

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BladeBootWait

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-wait-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBladeBootWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BladePowerOn

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: power on server [chassisId]/[slotId] for discovery(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBladePowerOn

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BladeReadSmbios

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for SMBIOS table from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-read-smbios-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBladeReadSmbios

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcConfigPnuOS

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcConfigPnuOS

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcInventory

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcPreConfigPnuOSLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-pre-config-pnuoslocal-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcPreConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcPreConfigPnuOSPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-pre-config-pnuospeer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcPreConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcPresence

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcPresence

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:BmcShutdownDiscovered

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown the server [chassisId]/[slotId]; deep discovery completed(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcShutdownDiscovered)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-discovered-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverBmcShutdownDiscovered

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:CheckPowerAvailability

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverCheckPowerAvailability

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:ConfigBMCPowerParams

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Configuring power profiling parameters for server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigBMCPowerParams)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configbmcpower-params-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverConfigBMCPowerParams

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:ConfigFeLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-local-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:ConfigFePeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-peer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:ConfigFlexFlashScrub

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Configuring FlexFlash Scrub on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverConfigFlexFlashScrub

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:ConfigUserAccess

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverConfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:HandlePooling

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Invoke post-discovery policies on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverHandlePooling

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicConfigPnuOSLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configure primary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicConfigPnuOSPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configure secondary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicPresenceLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresenceLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-local-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicPresenceLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicPresencePeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresencePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-peer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicPresencePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicUnconfigPnuOSLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicUnconfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:NicUnconfigPnuOSPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverNicUnconfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:OobStorageInventory

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Perform oob storage inventory of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverOobStorageInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSCatalog

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSCatalog

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSIdent

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSIdent

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSInventory

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Perform inventory of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSPolicy

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSPolicy

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSPowerProfiling

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Profile power for server [chassisId]/[slotId] by running benchmark(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSPowerProfiling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospower-profiling-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSPowerProfiling

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSScrub

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Scrub server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSScrub

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PnuOSSelfTest

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Trigger self-test of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPnuOSSelfTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PowerDeployWait

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPowerDeployWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PreSanitize

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPreSanitize

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:PrepareKeyFile

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:ComputeBladeDiscover:PrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-key-file-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverPrepareKeyFile

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:Sanitize

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSanitize

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SendBmcProfilingDone

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for valid power profile for server [chassisId]/[slotId] from CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:SendBmcProfilingDone)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bmc-profiling-done-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSendBmcProfilingDone

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SendBmcProfilingInit

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Start profiling power for server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:SendBmcProfilingInit)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bmc-profiling-init-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSendBmcProfilingInit

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SetupVmediaLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-local-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSetupVmediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SetupVmediaPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-peer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSetupVmediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SolRedirectDisable

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSolRedirectDisable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SolRedirectEnable

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSolRedirectEnable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SwConfigPnuOSLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configure primary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSwConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SwConfigPnuOSPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: configure secondary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSwConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SwUnconfigPnuOSLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSwUnconfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:SwUnconfigPnuOSPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSwUnconfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:TeardownVmediaLocal

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the Virtual Media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-local-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverTeardownVmediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:TeardownVmediaPeer

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the Virtual media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-peer-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverTeardownVmediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:UnconfigCimcVMedia

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverUnconfigCimcVMedia

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:UnconfigExtMgmtGw

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverUnconfigExtMgmtGw

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:UnconfigExtMgmtRules

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverUnconfigExtMgmtRules

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:hagConnect

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-connect-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverHagConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:hagDisconnect

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-disconnect-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverHagDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:serialDebugConnect

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSerialDebugConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiscover:serialDebugDisconnect

Fault Code: F16520

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 16520

mibFaultName: fsmStFailComputeBladeDiscoverSerialDebugDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailEquipmentChassisPsuPolicyConfig:Execute

Fault Code: F16533

Message

[FSM:STAGE:FAILED|RETRY]: Deploying Power Management policy changes on chassis [id](FSM-STAGE:sam:dme:EquipmentChassisPsuPolicyConfig:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16533

mibFaultName: fsmStFailEquipmentChassisPsuPolicyConfigExecute

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailAdaptorHostFcIfResetFcPersBinding:ExecuteLocal

Fault Code: F16534

Message

[FSM:STAGE:FAILED|RETRY]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 16534

mibFaultName: fsmStFailAdaptorHostFcIfResetFcPersBindingExecuteLocal

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailAdaptorHostFcIfResetFcPersBinding:ExecutePeer

Fault Code: F16534

Message

[FSM:STAGE:FAILED|RETRY]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 16534

mibFaultName: fsmStFailAdaptorHostFcIfResetFcPersBindingExecutePeer

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailComputeBladeDiag:BiosPostCompletion

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBiosPostCompletion

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BladeBoot

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Power-on server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBladeBoot

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BladeBootWait

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-wait-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBladeBootWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BladePowerOn

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Power on server [chassisId]/[slotId] for diagnostics(FSM-STAGE:sam:dme:ComputeBladeDiag:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBladePowerOn

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BladeReadSmbios

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Read SMBIOS tables on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-read-smbios-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBladeReadSmbios

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BmcConfigPnuOS

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBmcConfigPnuOS

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BmcInventory

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBmcInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BmcPresence

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBmcPresence

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:BmcShutdownDiagCompleted

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcShutdownDiagCompleted)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-diag-completed-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagBmcShutdownDiagCompleted

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:CleanupServerConnSwA

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning up server [chassisId]/[slotId] interface on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-server-conn-sw-afailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagCleanupServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:CleanupServerConnSwB

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning up server [chassisId]/[slotId] interface on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-server-conn-sw-bfailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagCleanupServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:ConfigFeLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:ConfigFePeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:ConfigUserAccess

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagConfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:DebugWait

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for debugging for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DebugWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debug-wait-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagDebugWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:DeriveConfig

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DeriveConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: derive-config-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagDeriveConfig

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:DisableServerConnSwA

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Disable server [chassisId]/[slotId] interface on fabric A after completion of network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-server-conn-sw-afailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagDisableServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:DisableServerConnSwB

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Disable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-server-conn-sw-bfailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagDisableServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:EnableServerConnSwA

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Enable server [chassisId]/[slotId] connectivity on fabric A in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-server-conn-sw-afailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagEnableServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:EnableServerConnSwB

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Enable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-server-conn-sw-bfailed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagEnableServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:EvaluateStatus

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Evaluating status; diagnostics completed(FSM-STAGE:sam:dme:ComputeBladeDiag:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagEvaluateStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:FabricATrafficTestStatus

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Gather status of network traffic tests on fabric A for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricATrafficTestStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: fabricatraffic-test-status-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagFabricATrafficTestStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:FabricBTrafficTestStatus

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Gather status of network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricBTrafficTestStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: fabricbtraffic-test-status-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagFabricBTrafficTestStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:GenerateLogWait

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for collection of diagnostic logs from server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateLogWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: generate-log-wait-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagGenerateLogWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:GenerateReport

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Generating report for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateReport)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: generate-report-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagGenerateReport

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostCatalog

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Populate diagnostics catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-catalog-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostCatalog

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostConnect

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Connect to diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-connect-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostDisconnect

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect diagnostics environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-disconnect-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostIdent

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Identify diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-ident-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostIdent

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostInventory

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Perform inventory of server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:HostInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-inventory-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostPolicy

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Populate diagnostics environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-policy-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostPolicy

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostServerDiag

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Trigger diagnostics on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiag)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-server-diag-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostServerDiag

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:HostServerDiagStatus

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Diagnostics status on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiagStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-server-diag-status-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagHostServerDiagStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicConfigLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicConfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicConfigPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicConfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicInventoryLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicInventoryLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicInventoryPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicInventoryPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicPresenceLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresenceLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicPresenceLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicPresencePeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresencePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicPresencePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicUnconfigLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicUnconfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:NicUnconfigPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagNicUnconfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:RemoveConfig

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-config-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagRemoveConfig

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:RemoveVMediaLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: removevmedia-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagRemoveVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:RemoveVMediaPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: removevmedia-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagRemoveVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:RestoreConfigFeLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Reconfiguring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-config-fe-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagRestoreConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:RestoreConfigFePeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Reconfiguring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-config-fe-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagRestoreConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SetDiagUser

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Populate diagnostics environment with a user account to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SetDiagUser)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-diag-user-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSetDiagUser

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SetupVMediaLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setupvmedia-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSetupVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SetupVMediaPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setupvmedia-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSetupVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SolRedirectDisable

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSolRedirectDisable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SolRedirectEnable

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSolRedirectEnable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:StartFabricATrafficTest

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Trigger network traffic tests on fabric A on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricATrafficTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-fabricatraffic-test-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagStartFabricATrafficTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:StartFabricBTrafficTest

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Trigger network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricBTrafficTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-fabricbtraffic-test-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagStartFabricBTrafficTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:StopVMediaLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagStopVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:StopVMediaPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagStopVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SwConfigLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSwConfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SwConfigPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSwConfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SwUnconfigLocal

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-local-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSwUnconfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:SwUnconfigPeer

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-peer-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSwUnconfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:UnconfigUserAccess

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:UnconfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-user-access-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagUnconfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:serialDebugConnect

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSerialDebugConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailComputeBladeDiag:serialDebugDisconnect

Fault Code: F16535

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 16535

mibFaultName: fsmStFailComputeBladeDiagSerialDebugDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmStFailFabricLanCloudSwitchMode:SwConfigLocal

Fault Code: F16539

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 16539

mibFaultName: fsmStFailFabricLanCloudSwitchModeSwConfigLocal

moClass: fabric:LanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan

fsmStFailFabricLanCloudSwitchMode:SwConfigPeer

Fault Code: F16539

Message

[FSM:STAGE:FAILED|RETRY]: Fabric interconnect mode configuration to primary(FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 16539

mibFaultName: fsmStFailFabricLanCloudSwitchModeSwConfigPeer

moClass: fabric:LanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan

fsmStFailVnicProfileSetDeploy:Local

Fault Code: F16550

Message

[FSM:STAGE:FAILED|RETRY]: VNIC profile configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16550

mibFaultName: fsmStFailVnicProfileSetDeployLocal

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmStFailVnicProfileSetDeploy:Peer

Fault Code: F16550

Message

[FSM:STAGE:FAILED|RETRY]: VNIC profile configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16550

mibFaultName: fsmStFailVnicProfileSetDeployPeer

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpSettings

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated settings (eg. timezone)(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpSettings)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-settings-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpSettings

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsLocal

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-local-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsPeer

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-peer-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsLocal

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-adaptors-local-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToAdaptorsLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsPeer

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-adaptors-peer-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToAdaptorsPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomLocal

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-fex-iom-local-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToFexIomLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomPeer

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-fex-iom-peer-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToFexIomPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:SetEpLocal

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: communication service [name] configuration to primary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-local-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpSetEpLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpUpdateSvcEp:SetEpPeer

Fault Code: F16576

Message

[FSM:STAGE:FAILED|RETRY]: communication service [name] configuration to secondary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-peer-failed

mibFaultCode: 16576

mibFaultName: fsmStFailCommSvcEpUpdateSvcEpSetEpPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpRestartWebSvc:local

Fault Code: F16577

Message

[FSM:STAGE:FAILED|RETRY]: restart web services in primary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16577

mibFaultName: fsmStFailCommSvcEpRestartWebSvcLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailCommSvcEpRestartWebSvc:peer

Fault Code: F16577

Message

[FSM:STAGE:FAILED|RETRY]: restart web services in secondary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16577

mibFaultName: fsmStFailCommSvcEpRestartWebSvcPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmStFailAaaEpUpdateEp:SetEpLocal

Fault Code: F16579

Message

[FSM:STAGE:FAILED|RETRY]: external aaa server configuration to primary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpLocal)

Explanation

Cisco FPR Manager could not set the configurations in the primary Fabric Interconnect for AAA servers while re-ordering/deleting providers.

Recommended Action

If you see this fault, take the following actions:

Step 1 1. Identify the auth-domain(s) that are using the auth-realm modification causing this fault.

Step 2 2. Modify the auth-domain(s) realm identified in step 1, to local realm and commit the changes.

Step 3 3. Re-order/Delete the AAA providers user wish to modify and commit the changes.

Step 4 4. Change the auth-domain(s) realm back to previous realm modified in step2 and commit the changes.

Fault Details

Severity: warning

Cause: set-ep-local-failed

mibFaultCode: 16579

mibFaultName: fsmStFailAaaEpUpdateEpSetEpLocal

moClass: aaa:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext

Affected MO: sys/radius-ext

Affected MO: sys/tacacs-ext

fsmStFailAaaEpUpdateEp:SetEpPeer

Fault Code: F16579

Message

[FSM:STAGE:FAILED|RETRY]: external aaa server configuration to secondary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpPeer)

Explanation

Cisco FPR Manager could not set the configurations in the secondary Fabric Interconnect for AAA servers while re-ordering/deleting providers.

Recommended Action

If you see this fault, take the following actions:

Step 1 0. Make sure secondary FI is up and running.

Step 2 1. Identify the auth-domain(s) that are using the auth-realm modification causing this fault.

Step 3 2. Modify the auth-domain(s) realm identified in step 1, to local realm and commit the changes.

Step 4 3. Re-order/Delete the AAA providers user wish to modify and commit the changes.

Step 5 4. Change the auth-domain(s) realm back to previous realm modified in step2 and commit the changes.

Fault Details

Severity: warning

Cause: set-ep-peer-failed

mibFaultCode: 16579

mibFaultName: fsmStFailAaaEpUpdateEpSetEpPeer

moClass: aaa:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext

Affected MO: sys/radius-ext

Affected MO: sys/tacacs-ext

fsmStFailAaaRealmUpdateRealm:SetRealmLocal

Fault Code: F16580

Message

[FSM:STAGE:FAILED|RETRY]: realm configuration to primary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmLocal)

Explanation

Cisco FPR Manager could not set the configurations in the primary Fabric Interconnect for Authentication realms.

Recommended Action

If you see this fault, take the following actions:

Step 1 1. Make sure the auth-server-group used in the auth-domain is exist and is deployed on to switch.

Step 2 2. If auth-server-group doesn’t exist, either create auth-server-group in appropriaate realm (RADIUS/TACACS+/LDAP) or unset the auth-server-group in auth-domain.

Fault Details

Severity: warning

Cause: set-realm-local-failed

mibFaultCode: 16580

mibFaultName: fsmStFailAaaRealmUpdateRealmSetRealmLocal

moClass: aaa:Realm

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm

fsmStFailAaaRealmUpdateRealm:SetRealmPeer

Fault Code: F16580

Message

[FSM:STAGE:FAILED|RETRY]: realm configuration to secondary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmPeer)

Explanation

Cisco FPR Manager could not set the configurations in the secondary Fabric Interconnect for Authentication realms.

Recommended Action

If you see this fault, take the following actions:

Step 1 0. Make sure secondary FI is up and running.

Step 2 1. Make sure the auth-server-group used in the auth-domain is exist and is deployed on to switch.

Step 3 2. If auth-server-group doesn’t exist, either create auth-server-group in appropriaate realm (RADIUS/TACACS+/LDAP) or unset the auth-server-group in auth-domain.

Fault Details

Severity: warning

Cause: set-realm-peer-failed

mibFaultCode: 16580

mibFaultName: fsmStFailAaaRealmUpdateRealmSetRealmPeer

moClass: aaa:Realm

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm

fsmStFailAaaUserEpUpdateUserEp:SetUserLocal

Fault Code: F16581

Message

[FSM:STAGE:FAILED|RETRY]: user configuration to primary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-user-local-failed

mibFaultCode: 16581

mibFaultName: fsmStFailAaaUserEpUpdateUserEpSetUserLocal

moClass: aaa:UserEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext

fsmStFailAaaUserEpUpdateUserEp:SetUserPeer

Fault Code: F16581

Message

[FSM:STAGE:FAILED|RETRY]: user configuration to secondary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-user-peer-failed

mibFaultCode: 16581

mibFaultName: fsmStFailAaaUserEpUpdateUserEpSetUserPeer

moClass: aaa:UserEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext

fsmStFailPkiEpUpdateEp:PostSetKeyRingLocal

Fault Code: F16582

Message

[FSM:STAGE:FAILED|RETRY]: post processing after keyring configration on primary(FSM-STAGE:sam:dme:PkiEpUpdateEp:PostSetKeyRingLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: post-set-key-ring-local-failed

mibFaultCode: 16582

mibFaultName: fsmStFailPkiEpUpdateEpPostSetKeyRingLocal

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmStFailPkiEpUpdateEp:PostSetKeyRingPeer

Fault Code: F16582

Message

[FSM:STAGE:FAILED|RETRY]: post processing after keyring configuration on secondary(FSM-STAGE:sam:dme:PkiEpUpdateEp:PostSetKeyRingPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: post-set-key-ring-peer-failed

mibFaultCode: 16582

mibFaultName: fsmStFailPkiEpUpdateEpPostSetKeyRingPeer

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmStFailPkiEpUpdateEp:SetKeyRingLocal

Fault Code: F16582

Message

[FSM:STAGE:FAILED|RETRY]: keyring configuration on primary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-key-ring-local-failed

mibFaultCode: 16582

mibFaultName: fsmStFailPkiEpUpdateEpSetKeyRingLocal

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmStFailPkiEpUpdateEp:SetKeyRingPeer

Fault Code: F16582

Message

[FSM:STAGE:FAILED|RETRY]: keyring configuration on secondary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-key-ring-peer-failed

mibFaultCode: 16582

mibFaultName: fsmStFailPkiEpUpdateEpSetKeyRingPeer

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmStFailSysfileMutationSingle:Execute

Fault Code: F16600

Message

[FSM:STAGE:FAILED|RETRY]: [action] file [name](FSM-STAGE:sam:dme:SysfileMutationSingle:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16600

mibFaultName: fsmStFailSysfileMutationSingleExecute

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmStFailSysfileMutationGlobal:Local

Fault Code: F16601

Message

[FSM:STAGE:FAILED|RETRY]: remove files from local(FSM-STAGE:sam:dme:SysfileMutationGlobal:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16601

mibFaultName: fsmStFailSysfileMutationGlobalLocal

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmStFailSysfileMutationGlobal:Peer

Fault Code: F16601

Message

[FSM:STAGE:FAILED|RETRY]: remove files from peer(FSM-STAGE:sam:dme:SysfileMutationGlobal:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16601

mibFaultName: fsmStFailSysfileMutationGlobalPeer

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmStFailSysdebugManualCoreFileExportTargetExport:Execute

Fault Code: F16604

Message

[FSM:STAGE:FAILED|RETRY]: export core file [name] to [hostname](FSM-STAGE:sam:dme:SysdebugManualCoreFileExportTargetExport:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16604

mibFaultName: fsmStFailSysdebugManualCoreFileExportTargetExportExecute

moClass: sysdebug:ManualCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/export-to-[hostname]

fsmStFailSysdebugAutoCoreFileExportTargetConfigure:Local

Fault Code: F16605

Message

[FSM:STAGE:FAILED|RETRY]: configuring automatic core file export service on local(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Local)

Explanation

Cisco Firepower Manager could not set the configurations in the primary Fabric Interconnect for auto core transfer to remote TFTP server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16605

mibFaultName: fsmStFailSysdebugAutoCoreFileExportTargetConfigureLocal

moClass: sysdebug:AutoCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fsmStFailSysdebugAutoCoreFileExportTargetConfigure:Peer

Fault Code: F16605

Message

[FSM:STAGE:FAILED|RETRY]: configuring automatic core file export service on peer(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Peer)

Explanation

Cisco Firepower Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for auto core transfer to remote TFTP server. This fault typically appears for one of the following reasons:

- The subordinate FI is not reachable.

- The subordinate FI is experiencing an internal system error on applying the configuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FI cluster state to ensure that the subordinate FI is reachable and functioning correctly. If the subordinate FI is down, take appropriate corrective actions so that the Firepower cluster goes into HA ready state.

Step 2 If the HA state of the primary and subordinate FIs are good, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16605

mibFaultName: fsmStFailSysdebugAutoCoreFileExportTargetConfigurePeer

moClass: sysdebug:AutoCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fsmStFailSysdebugLogControlEpLogControlPersist:Local

Fault Code: F16606

Message

[FSM:STAGE:FAILED|RETRY]: persisting LogControl on local(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16606

mibFaultName: fsmStFailSysdebugLogControlEpLogControlPersistLocal

moClass: sysdebug:LogControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/logcontrol

fsmStFailSysdebugLogControlEpLogControlPersist:Peer

Fault Code: F16606

Message

[FSM:STAGE:FAILED|RETRY]: persisting LogControl on peer(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16606

mibFaultName: fsmStFailSysdebugLogControlEpLogControlPersistPeer

moClass: sysdebug:LogControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/logcontrol

fsmStFailSwAccessDomainDeploy:UpdateConnectivity

Fault Code: F16634

Message

[FSM:STAGE:FAILED|RETRY]: internal network configuration on [switchId](FSM-STAGE:sam:dme:SwAccessDomainDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 16634

mibFaultName: fsmStFailSwAccessDomainDeployUpdateConnectivity

moClass: sw:AccessDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/access-eth

fsmStFailSwEthLanBorderDeploy:UpdateConnectivity

Fault Code: F16635

Message

[FSM:STAGE:FAILED|RETRY]: Uplink eth port configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 16635

mibFaultName: fsmStFailSwEthLanBorderDeployUpdateConnectivity

moClass: sw:EthLanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-eth

fsmStFailSwEthLanBorderDeploy:UpdateVlanGroups

Fault Code: F16635

Message

[FSM:STAGE:FAILED|RETRY]: VLAN group configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateVlanGroups)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-vlan-groups-failed

mibFaultCode: 16635

mibFaultName: fsmStFailSwEthLanBorderDeployUpdateVlanGroups

moClass: sw:EthLanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-eth

fsmStFailSwFcSanBorderDeploy:UpdateConnectivity

Fault Code: F16636

Message

[FSM:STAGE:FAILED|RETRY]: Uplink fc port configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 16636

mibFaultName: fsmStFailSwFcSanBorderDeployUpdateConnectivity

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmStFailSwUtilityDomainDeploy:UpdateConnectivity

Fault Code: F16637

Message

[FSM:STAGE:FAILED|RETRY]: Utility network configuration on [switchId](FSM-STAGE:sam:dme:SwUtilityDomainDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 16637

mibFaultName: fsmStFailSwUtilityDomainDeployUpdateConnectivity

moClass: sw:UtilityDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/utility-eth

fsmStFailSyntheticFsObjCreate:createLocal

Fault Code: F16641

Message

[FSM:STAGE:FAILED|RETRY]: create on primary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: create-local-failed

mibFaultCode: 16641

mibFaultName: fsmStFailSyntheticFsObjCreateCreateLocal

moClass: synthetic:FsObj

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/file-[name]

fsmStFailSyntheticFsObjCreate:createRemote

Fault Code: F16641

Message

[FSM:STAGE:FAILED|RETRY]: create on secondary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: create-remote-failed

mibFaultCode: 16641

mibFaultName: fsmStFailSyntheticFsObjCreateCreateRemote

moClass: synthetic:FsObj

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/file-[name]

fsmStFailFirmwareDownloaderDownload:CopyRemote

Fault Code: F16650

Message

[FSM:STAGE:FAILED|RETRY]: sync images to subordinate(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 16650

mibFaultName: fsmStFailFirmwareDownloaderDownloadCopyRemote

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmStFailFirmwareDownloaderDownload:DeleteLocal

Fault Code: F16650

Message

[FSM:STAGE:FAILED|RETRY]: deleting downloadable [fileName] on local(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 16650

mibFaultName: fsmStFailFirmwareDownloaderDownloadDeleteLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmStFailFirmwareDownloaderDownload:Local

Fault Code: F16650

Message

[FSM:STAGE:FAILED|RETRY]: downloading image or file [fileName] from [server](FSM-STAGE:sam:dme:FirmwareDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16650

mibFaultName: fsmStFailFirmwareDownloaderDownloadLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmStFailFirmwareDownloaderDownload:UnpackLocal

Fault Code: F16650

Message

[FSM:STAGE:FAILED|RETRY]: unpacking image [fileName] on primary(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 16650

mibFaultName: fsmStFailFirmwareDownloaderDownloadUnpackLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmStFailFirmwareImageDelete:Local

Fault Code: F16651

Message

[FSM:STAGE:FAILED|RETRY]: deleting image file [name] ([invTag]) from primary(FSM-STAGE:sam:dme:FirmwareImageDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16651

mibFaultName: fsmStFailFirmwareImageDeleteLocal

moClass: firmware:Image

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/image-[name]

Affected MO: sys/fw-catalogue/image-[name]

fsmStFailFirmwareImageDelete:Remote

Fault Code: F16651

Message

[FSM:STAGE:FAILED|RETRY]: deleting image file [name] ([invTag]) from secondary(FSM-STAGE:sam:dme:FirmwareImageDelete:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 16651

mibFaultName: fsmStFailFirmwareImageDeleteRemote

moClass: firmware:Image

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/image-[name]

Affected MO: sys/fw-catalogue/image-[name]

fsmStFailMgmtControllerUpdateSwitch:copyToLocal

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-to-local-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchCopyToLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:copyToPeer

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-to-peer-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchCopyToPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:resetLocal

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: rebooting local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-local-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchResetLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:resetRemote

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: rebooting remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-remote-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchResetRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:updateLocal

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: updating local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-local-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchUpdateLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:updateRemote

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: updating peer fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-remote-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchUpdateRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:verifyLocal

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: verifying boot variables for local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-local-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchVerifyLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateSwitch:verifyRemote

Fault Code: F16653

Message

[FSM:STAGE:FAILED|RETRY]: verifying boot variables for remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-remote-failed

mibFaultCode: 16653

mibFaultName: fsmStFailMgmtControllerUpdateSwitchVerifyRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateIOM:CopyIOMImgToSub

Fault Code: F16654

Message

[FSM:STAGE:FAILED|RETRY]: Copying IOM Image to subordinate FI(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:CopyIOMImgToSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copyiomimg-to-sub-failed

mibFaultCode: 16654

mibFaultName: fsmStFailMgmtControllerUpdateIOMCopyIOMImgToSub

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateIOM:CopyImgFromRep

Fault Code: F16654

Message

[FSM:STAGE:FAILED|RETRY]: Copying IOM Image from repository to FI(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:CopyImgFromRep)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-img-from-rep-failed

mibFaultCode: 16654

mibFaultName: fsmStFailMgmtControllerUpdateIOMCopyImgFromRep

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateIOM:PollUpdateStatus

Fault Code: F16654

Message

[FSM:STAGE:FAILED|RETRY]: waiting for IOM update(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 16654

mibFaultName: fsmStFailMgmtControllerUpdateIOMPollUpdateStatus

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateIOM:UpdateRequest

Fault Code: F16654

Message

[FSM:STAGE:FAILED|RETRY]: sending update request to IOM(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 16654

mibFaultName: fsmStFailMgmtControllerUpdateIOMUpdateRequest

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerActivateIOM:Activate

Fault Code: F16655

Message

[FSM:STAGE:FAILED|RETRY]: activating backup image of IOM(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 16655

mibFaultName: fsmStFailMgmtControllerActivateIOMActivate

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerActivateIOM:Reset

Fault Code: F16655

Message

[FSM:STAGE:FAILED|RETRY]: Resetting IOM to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 16655

mibFaultName: fsmStFailMgmtControllerActivateIOMReset

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateBMC:PollUpdateStatus

Fault Code: F16656

Message

[FSM:STAGE:FAILED|RETRY]: waiting for update to complete(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 16656

mibFaultName: fsmStFailMgmtControllerUpdateBMCPollUpdateStatus

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateBMC:UpdateRequest

Fault Code: F16656

Message

[FSM:STAGE:FAILED|RETRY]: sending update request to CIMC(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 16656

mibFaultName: fsmStFailMgmtControllerUpdateBMCUpdateRequest

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerActivateBMC:Activate

Fault Code: F16657

Message

[FSM:STAGE:FAILED|RETRY]: activating backup image of CIMC(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 16657

mibFaultName: fsmStFailMgmtControllerActivateBMCActivate

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerActivateBMC:Reset

Fault Code: F16657

Message

[FSM:STAGE:FAILED|RETRY]: Resetting CIMC to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 16657

mibFaultName: fsmStFailMgmtControllerActivateBMCReset

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailCallhomeEpConfigCallhome:SetLocal

Fault Code: F16670

Message

[FSM:STAGE:FAILED|RETRY]: call-home configuration on primary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 16670

mibFaultName: fsmStFailCallhomeEpConfigCallhomeSetLocal

moClass: callhome:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fsmStFailCallhomeEpConfigCallhome:SetPeer

Fault Code: F16670

Message

[FSM:STAGE:FAILED|RETRY]: call-home configuration on secondary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 16670

mibFaultName: fsmStFailCallhomeEpConfigCallhomeSetPeer

moClass: callhome:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fsmStFailMgmtIfSwMgmtOobIfConfig:Switch

Fault Code: F16673

Message

[FSM:STAGE:FAILED|RETRY]: configuring the out-of-band interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtOobIfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 16673

mibFaultName: fsmStFailMgmtIfSwMgmtOobIfConfigSwitch

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfSwMgmtInbandIfConfig:Switch

Fault Code: F16674

Message

[FSM:STAGE:FAILED|RETRY]: configuring the inband interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtInbandIfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 16674

mibFaultName: fsmStFailMgmtIfSwMgmtInbandIfConfigSwitch

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfVirtualIfConfig:Local

Fault Code: F16679

Message

[FSM:STAGE:FAILED|RETRY]: Updating virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16679

mibFaultName: fsmStFailMgmtIfVirtualIfConfigLocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfVirtualIfConfig:Remote

Fault Code: F16679

Message

[FSM:STAGE:FAILED|RETRY]: Updating virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 16679

mibFaultName: fsmStFailMgmtIfVirtualIfConfigRemote

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfEnableVip:Local

Fault Code: F16680

Message

[FSM:STAGE:FAILED|RETRY]: Enable virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfEnableVip:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16680

mibFaultName: fsmStFailMgmtIfEnableVipLocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfDisableVip:Peer

Fault Code: F16681

Message

[FSM:STAGE:FAILED|RETRY]: Disable virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfDisableVip:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16681

mibFaultName: fsmStFailMgmtIfDisableVipPeer

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtIfEnableHA:Local

Fault Code: F16682

Message

[FSM:STAGE:FAILED|RETRY]: Transition from single to cluster mode(FSM-STAGE:sam:dme:MgmtIfEnableHA:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16682

mibFaultName: fsmStFailMgmtIfEnableHALocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmStFailMgmtBackupBackup:backupLocal

Fault Code: F16683

Message

[FSM:STAGE:FAILED|RETRY]: internal database backup(FSM-STAGE:sam:dme:MgmtBackupBackup:backupLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: backup-local-failed

mibFaultCode: 16683

mibFaultName: fsmStFailMgmtBackupBackupBackupLocal

moClass: mgmt:Backup

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/backup-[hostname]

fsmStFailMgmtBackupBackup:upload

Fault Code: F16683

Message

[FSM:STAGE:FAILED|RETRY]: internal system backup(FSM-STAGE:sam:dme:MgmtBackupBackup:upload)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upload-failed

mibFaultCode: 16683

mibFaultName: fsmStFailMgmtBackupBackupUpload

moClass: mgmt:Backup

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/backup-[hostname]

fsmStFailMgmtImporterImport:cleanUp

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: cleaning up old Security Service configuration(FSM-STAGE:sam:dme:MgmtImporterImport:cleanUp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clean-up-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportCleanUp

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailMgmtImporterImport:config

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: importing the configuration file(FSM-STAGE:sam:dme:MgmtImporterImport:config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportConfig

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailMgmtImporterImport:configBreakout

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: updating breakout port configuration(FSM-STAGE:sam:dme:MgmtImporterImport:configBreakout)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-breakout-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportConfigBreakout

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailMgmtImporterImport:downloadLocal

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: downloading the configuration file(FSM-STAGE:sam:dme:MgmtImporterImport:downloadLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-local-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportDownloadLocal

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailMgmtImporterImport:reportResults

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: Reporting results of import configuration(FSM-STAGE:sam:dme:MgmtImporterImport:reportResults)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-results-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportReportResults

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailMgmtImporterImport:waitForSwitch

Fault Code: F16684

Message

[FSM:STAGE:FAILED|RETRY]: waiting for completion of switch configuration(FSM-STAGE:sam:dme:MgmtImporterImport:waitForSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-failed

mibFaultCode: 16684

mibFaultName: fsmStFailMgmtImporterImportWaitForSwitch

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmStFailStatsCollectionPolicyUpdateEp:SetEpA

Fault Code: F16742

Message

[FSM:STAGE:FAILED|RETRY]: Update endpoint on fabric interconnect A(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-afailed

mibFaultCode: 16742

mibFaultName: fsmStFailStatsCollectionPolicyUpdateEpSetEpA

moClass: stats:CollectionPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: stats/coll-policy-[name]

fsmStFailStatsCollectionPolicyUpdateEp:SetEpB

Fault Code: F16742

Message

[FSM:STAGE:FAILED|RETRY]: Update endpoint on fabric interconnect B(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-bfailed

mibFaultCode: 16742

mibFaultName: fsmStFailStatsCollectionPolicyUpdateEpSetEpB

moClass: stats:CollectionPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: stats/coll-policy-[name]

fsmStFailQosclassDefinitionConfigGlobalQoS:SetLocal

Fault Code: F16745

Message

[FSM:STAGE:FAILED|RETRY]: QoS Classification Definition [name] configuration on primary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 16745

mibFaultName: fsmStFailQosclassDefinitionConfigGlobalQoSSetLocal

moClass: qosclass:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/classes

fsmStFailQosclassDefinitionConfigGlobalQoS:SetPeer

Fault Code: F16745

Message

[FSM:STAGE:FAILED|RETRY]: QoS Classification Definition [name] configuration on secondary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 16745

mibFaultName: fsmStFailQosclassDefinitionConfigGlobalQoSSetPeer

moClass: qosclass:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/classes

fsmStFailEpqosDefinitionDeploy:Local

Fault Code: F16749

Message

[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] configuration to primary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16749

mibFaultName: fsmStFailEpqosDefinitionDeployLocal

moClass: epqos:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-[name]

fsmStFailEpqosDefinitionDeploy:Peer

Fault Code: F16749

Message

[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] configuration to secondary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16749

mibFaultName: fsmStFailEpqosDefinitionDeployPeer

moClass: epqos:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-[name]

fsmStFailEpqosDefinitionDelTaskRemove:Local

Fault Code: F16750

Message

[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] removal from primary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16750

mibFaultName: fsmStFailEpqosDefinitionDelTaskRemoveLocal

moClass: epqos:DefinitionDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-deletion-[defIntId]

fsmStFailEpqosDefinitionDelTaskRemove:Peer

Fault Code: F16750

Message

[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] removal from secondary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 16750

mibFaultName: fsmStFailEpqosDefinitionDelTaskRemovePeer

moClass: epqos:DefinitionDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-deletion-[defIntId]

fsmStFailEquipmentIOCardResetCmc:Execute

Fault Code: F16803

Message

[FSM:STAGE:FAILED|RETRY]: Resetting Chassis Management Controller on IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardResetCmc:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16803

mibFaultName: fsmStFailEquipmentIOCardResetCmcExecute

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailMgmtControllerUpdateUCSManager:copyExtToLocal

Fault Code: F16815

Message

[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-ext-to-local-failed

mibFaultCode: 16815

mibFaultName: fsmStFailMgmtControllerUpdateUCSManagerCopyExtToLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateUCSManager:copyExtToPeer

Fault Code: F16815

Message

[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-ext-to-peer-failed

mibFaultCode: 16815

mibFaultName: fsmStFailMgmtControllerUpdateUCSManagerCopyExtToPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateUCSManager:execute

Fault Code: F16815

Message

[FSM:STAGE:FAILED|RETRY]: Updating FPR Manager firmware(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16815

mibFaultName: fsmStFailMgmtControllerUpdateUCSManagerExecute

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerUpdateUCSManager:start

Fault Code: F16815

Message

[FSM:STAGE:FAILED|RETRY]: Scheduling FPR manager update(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 16815

mibFaultName: fsmStFailMgmtControllerUpdateUCSManagerStart

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerSysConfig:Primary

Fault Code: F16823

Message

[FSM:STAGE:FAILED|RETRY]: system configuration on primary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Primary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: primary-failed

mibFaultCode: 16823

mibFaultName: fsmStFailMgmtControllerSysConfigPrimary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerSysConfig:Secondary

Fault Code: F16823

Message

[FSM:STAGE:FAILED|RETRY]: system configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Secondary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: secondary-failed

mibFaultCode: 16823

mibFaultName: fsmStFailMgmtControllerSysConfigSecondary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailAdaptorExtEthIfPathReset:Disable

Fault Code: F16852

Message

[FSM:STAGE:FAILED|RETRY]: Disable path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Disable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-failed

mibFaultCode: 16852

mibFaultName: fsmStFailAdaptorExtEthIfPathResetDisable

moClass: adaptor:ExtEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fsmStFailAdaptorExtEthIfPathReset:Enable

Fault Code: F16852

Message

[FSM:STAGE:FAILED|RETRY]: Enabe path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Enable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-failed

mibFaultCode: 16852

mibFaultName: fsmStFailAdaptorExtEthIfPathResetEnable

moClass: adaptor:ExtEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fsmStFailAdaptorHostEthIfCircuitReset:DisableA

Fault Code: F16857

Message

[FSM:STAGE:FAILED|RETRY]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-afailed

mibFaultCode: 16857

mibFaultName: fsmStFailAdaptorHostEthIfCircuitResetDisableA

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmStFailAdaptorHostEthIfCircuitReset:DisableB

Fault Code: F16857

Message

[FSM:STAGE:FAILED|RETRY]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-bfailed

mibFaultCode: 16857

mibFaultName: fsmStFailAdaptorHostEthIfCircuitResetDisableB

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmStFailAdaptorHostEthIfCircuitReset:EnableA

Fault Code: F16857

Message

[FSM:STAGE:FAILED|RETRY]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-afailed

mibFaultCode: 16857

mibFaultName: fsmStFailAdaptorHostEthIfCircuitResetEnableA

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmStFailAdaptorHostEthIfCircuitReset:EnableB

Fault Code: F16857

Message

[FSM:STAGE:FAILED|RETRY]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-bfailed

mibFaultCode: 16857

mibFaultName: fsmStFailAdaptorHostEthIfCircuitResetEnableB

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmStFailAdaptorHostFcIfCircuitReset:DisableA

Fault Code: F16858

Message

[FSM:STAGE:FAILED|RETRY]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-afailed

mibFaultCode: 16858

mibFaultName: fsmStFailAdaptorHostFcIfCircuitResetDisableA

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailAdaptorHostFcIfCircuitReset:DisableB

Fault Code: F16858

Message

[FSM:STAGE:FAILED|RETRY]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-bfailed

mibFaultCode: 16858

mibFaultName: fsmStFailAdaptorHostFcIfCircuitResetDisableB

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailAdaptorHostFcIfCircuitReset:EnableA

Fault Code: F16858

Message

[FSM:STAGE:FAILED|RETRY]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-afailed

mibFaultCode: 16858

mibFaultName: fsmStFailAdaptorHostFcIfCircuitResetEnableA

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailAdaptorHostFcIfCircuitReset:EnableB

Fault Code: F16858

Message

[FSM:STAGE:FAILED|RETRY]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-bfailed

mibFaultCode: 16858

mibFaultName: fsmStFailAdaptorHostFcIfCircuitResetEnableB

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmStFailExtvmmProviderConfig:GetVersion

Fault Code: F16879

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager version fetch(FSM-STAGE:sam:dme:ExtvmmProviderConfig:GetVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: get-version-failed

mibFaultCode: 16879

mibFaultName: fsmStFailExtvmmProviderConfigGetVersion

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmStFailExtvmmProviderConfig:SetLocal

Fault Code: F16879

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 16879

mibFaultName: fsmStFailExtvmmProviderConfigSetLocal

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmStFailExtvmmProviderConfig:SetPeer

Fault Code: F16879

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 16879

mibFaultName: fsmStFailExtvmmProviderConfigSetPeer

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmStFailExtvmmKeyStoreCertInstall:SetLocal

Fault Code: F16880

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager cetificate configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 16880

mibFaultName: fsmStFailExtvmmKeyStoreCertInstallSetLocal

moClass: extvmm:KeyStore

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/key-store

fsmStFailExtvmmKeyStoreCertInstall:SetPeer

Fault Code: F16880

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager certificate configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 16880

mibFaultName: fsmStFailExtvmmKeyStoreCertInstallSetPeer

moClass: extvmm:KeyStore

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/key-store

fsmStFailExtvmmSwitchDelTaskRemoveProvider:RemoveLocal

Fault Code: F16881

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager deletion from local fabric(FSM-STAGE:sam:dme:ExtvmmSwitchDelTaskRemoveProvider:RemoveLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-local-failed

mibFaultCode: 16881

mibFaultName: fsmStFailExtvmmSwitchDelTaskRemoveProviderRemoveLocal

moClass: extvmm:SwitchDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vsw-deltask-[swIntId]

fsmStFailExtvmmMasterExtKeyConfig:SetLocal

Fault Code: F16898

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager extension-key configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 16898

mibFaultName: fsmStFailExtvmmMasterExtKeyConfigSetLocal

moClass: extvmm:MasterExtKey

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/ext-key

fsmStFailExtvmmMasterExtKeyConfig:SetPeer

Fault Code: F16898

Message

[FSM:STAGE:FAILED|RETRY]: external VM manager extension-key configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 16898

mibFaultName: fsmStFailExtvmmMasterExtKeyConfigSetPeer

moClass: extvmm:MasterExtKey

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/ext-key

fsmStFailCapabilityUpdaterUpdater:Apply

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Apply)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterApply

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:CopyRemote

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: syncing catalog files to subordinate(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterCopyRemote

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:DeleteLocal

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: deleting temp image [fileName] on local(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterDeleteLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:EvaluateStatus

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: evaluating status of update(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterEvaluateStatus

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:Local

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: downloading catalog file [fileName] from [server](FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:RescanImages

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: rescanning image files(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterRescanImages

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailCapabilityUpdaterUpdater:UnpackLocal

Fault Code: F16904

Message

[FSM:STAGE:FAILED|RETRY]: unpacking catalog file [fileName] on primary(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 16904

mibFaultName: fsmStFailCapabilityUpdaterUpdaterUnpackLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmStFailFirmwareDistributableDelete:Local

Fault Code: F16906

Message

[FSM:STAGE:FAILED|RETRY]: deleting package [name] from primary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 16906

mibFaultName: fsmStFailFirmwareDistributableDeleteLocal

moClass: firmware:Distributable

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]

fsmStFailFirmwareDistributableDelete:Remote

Fault Code: F16906

Message

[FSM:STAGE:FAILED|RETRY]: deleting package [name] from secondary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 16906

mibFaultName: fsmStFailFirmwareDistributableDeleteRemote

moClass: firmware:Distributable

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]

fsmStFailCapabilityCatalogueDeployCatalogue:SyncBladeAGLocal

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-bladeaglocal-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncBladeAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncBladeAGRemote

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-bladeagremote-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncBladeAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncHostagentAGLocal

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-hostagentaglocal-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncHostagentAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncHostagentAGRemote

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-hostagentagremote-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncHostagentAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncNicAGLocal

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-nicaglocal-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncNicAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncNicAGRemote

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-nicagremote-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncNicAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncPortAGLocal

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-portaglocal-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncPortAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:SyncPortAGRemote

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-portagremote-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueSyncPortAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueDeployCatalogue:finalize

Fault Code: F16931

Message

[FSM:STAGE:FAILED|RETRY]: Finalizing capability catalogue [version] deployment(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:finalize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: finalize-failed

mibFaultCode: 16931

mibFaultName: fsmStFailCapabilityCatalogueDeployCatalogueFinalize

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailEquipmentFexRemoveFex:CleanupEntries

Fault Code: F16942

Message

[FSM:STAGE:FAILED|RETRY]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:CleanupEntries)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-entries-failed

mibFaultCode: 16942

mibFaultName: fsmStFailEquipmentFexRemoveFexCleanupEntries

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmStFailEquipmentFexRemoveFex:UnIdentifyLocal

Fault Code: F16942

Message

[FSM:STAGE:FAILED|RETRY]: erasing fex identity [id] from primary(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:UnIdentifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-local-failed

mibFaultCode: 16942

mibFaultName: fsmStFailEquipmentFexRemoveFexUnIdentifyLocal

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmStFailEquipmentFexRemoveFex:Wait

Fault Code: F16942

Message

[FSM:STAGE:FAILED|RETRY]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 16942

mibFaultName: fsmStFailEquipmentFexRemoveFexWait

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmStFailEquipmentFexRemoveFex:decomission

Fault Code: F16942

Message

[FSM:STAGE:FAILED|RETRY]: decomissioning fex [id](FSM-STAGE:sam:dme:EquipmentFexRemoveFex:decomission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: decomission-failed

mibFaultCode: 16942

mibFaultName: fsmStFailEquipmentFexRemoveFexDecomission

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmStFailEquipmentLocatorLedSetFeLocatorLed:Execute

Fault Code: F16943

Message

[FSM:STAGE:FAILED|RETRY]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFeLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16943

mibFaultName: fsmStFailEquipmentLocatorLedSetFeLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmStFailEquipmentChassisPowerCap:Config

Fault Code: F16944

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:EquipmentChassisPowerCap:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 16944

mibFaultName: fsmStFailEquipmentChassisPowerCapConfig

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentIOCardMuxOffline:CleanupEntries

Fault Code: F16945

Message

[FSM:STAGE:FAILED|RETRY]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentIOCardMuxOffline:CleanupEntries)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-entries-failed

mibFaultCode: 16945

mibFaultName: fsmStFailEquipmentIOCardMuxOfflineCleanupEntries

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailComputePhysicalAssociate:ActivateBios

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:ActivateBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-bios-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateActivateBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BiosImgUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-img-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBiosImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BiosPostCompletion

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BladePowerOff

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Power off server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBladePowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BmcConfigPnuOS

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BmcPreconfigPnuOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BmcPreconfigPnuOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BmcUnconfigPnuOS

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BootHost

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Boot host OS for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootHost)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-host-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBootHost

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BootPnuos

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Bring-up pre-boot environment for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:BootWait

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:CheckPowerAvailability

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ClearBiosUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ClearBiosUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-bios-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateClearBiosUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigCimcVMedia

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: configuring mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-cimcvmedia-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigExtMgmtGw

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: configuring ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-ext-mgmt-gw-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigExtMgmtRules

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: configuring ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-ext-mgmt-rules-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigFlexFlash

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configuring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigFlexFlash)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigFlexFlash

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigSoL

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configuring SoL interface on server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigSoL)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-so-lfailed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigUserAccess

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigUserAccess

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:ConfigUuid

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure logical UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-uuid-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateConfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:DeassertResetBypass

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:DeleteCurlDownloadedImages

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Delete images downloaded from operations manager(FSM-STAGE:sam:dme:ComputePhysicalAssociate:DeleteCurlDownloadedImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-curl-downloaded-images-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateDeleteCurlDownloadedImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:GraphicsImageUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update gpu firmware image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:GraphicsImageUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: graphics-image-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateGraphicsImageUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:HbaImgUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HbaImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hba-img-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHbaImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:HostOSConfig

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure host OS components on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosconfig-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHostOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:HostOSIdent

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Identify host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosident-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHostOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:HostOSPolicy

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Upload host agent policy to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostospolicy-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHostOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:HostOSValidate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Validate host OS on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosvalidate-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHostOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:LocalDiskFwUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:LocalDiskFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-disk-fw-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateLocalDiskFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:MarkAdapterForReboot

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:MarkAdapterForReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mark-adapter-for-reboot-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateMarkAdapterForReboot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigHostOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-hostoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigHostOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-hostospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigPnuOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigPnuOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigServiceInfraLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-service-infra-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicConfigServiceInfraPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-service-infra-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicConfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicImgUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-img-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicUnconfigPnuOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:NicUnconfigPnuOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:OobStorageInventory

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Perform oob storage inventory with server profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateOobStorageInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSCatalog

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSConfig

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconfig-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSIdent

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSInventory

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSLocalDiskConfig

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure local disk on server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSLocalDiskConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoslocal-disk-config-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSLocalDiskConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSPolicy

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSSelfTest

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSUnloadDrivers

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Unload drivers on server with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSUnloadDrivers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunload-drivers-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSUnloadDrivers

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PnuOSValidate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Pre-boot environment validation for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PollBiosActivateStatus

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-activate-status-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePollBiosActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PollBiosUpdateStatus

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-update-status-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePollBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PollBoardCtrlUpdateStatus

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBoardCtrlUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-board-ctrl-update-status-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePollBoardCtrlUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PollClearBiosUpdateStatus

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollClearBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-bios-update-status-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePollClearBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PowerDeployWait

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PowerOn

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Power on server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PowerOnPreConfig

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: PowerOn preconfig for server of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerOnPreConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-pre-config-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePowerOnPreConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PreSanitize

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PrepareForBoot

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Prepare server for booting host OS(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PrepareForBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-for-boot-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePrepareForBoot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:PrepareKeyFile

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-key-file-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociatePrepareKeyFile

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:Sanitize

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SolRedirectDisable

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SolRedirectEnable

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token for server [assignedToDn] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:StorageCtlrImgUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:StorageCtlrImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: storage-ctlr-img-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateStorageCtlrImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigHostOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for server host os (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-hostoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigHostOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for server host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-hostospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigPnuOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigPnuOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigPortNivLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigPortNivPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigServiceInfraLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-service-infra-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwConfigServiceInfraPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Configure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-service-infra-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwConfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwUnconfigPnuOSLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SwUnconfigPnuOSPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:SyncPowerState

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Sync power state for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SyncPowerState)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-power-state-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSyncPowerState

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:UnconfigCimcVMedia

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:UnconfigExtMgmtGw

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:UnconfigExtMgmtRules

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:UpdateBiosRequest

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBiosRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bios-request-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateBiosRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:UpdateBoardCtrlRequest

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBoardCtrlRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-board-ctrl-request-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateBoardCtrlRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:VerifyFcZoneConfig

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalAssociate:VerifyFcZoneConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-fc-zone-config-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateVerifyFcZoneConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:activateAdaptorNwFwLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateActivateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:activateAdaptorNwFwPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateActivateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:activateIBMCFw

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateibmcfw-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateActivateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:copyRemote

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Copy images to peer node(FSM-STAGE:sam:dme:ComputePhysicalAssociate:copyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateCopyRemote

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:downloadImages

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Download images from operations manager(FSM-STAGE:sam:dme:ComputePhysicalAssociate:downloadImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-images-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateDownloadImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:hagHostOSConnect

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Connect to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagHostOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-hostosconnect-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHagHostOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:hagPnuOSConnect

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:hagPnuOSDisconnect

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:resetIBMC

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:resetIBMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resetibmc-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateResetIBMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:serialDebugPnuOSConnect

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:serialDebugPnuOSDisconnect

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:sspUpdateHostPreBoot

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Provisioning a SSP Blade with Firepower related config before boot for host(FSM-STAGE:sam:dme:ComputePhysicalAssociate:sspUpdateHostPreBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: ssp-update-host-pre-boot-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateSspUpdateHostPreBoot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:updateAdaptorNwFwLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:updateAdaptorNwFwPeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:updateIBMCFw

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateibmcfw-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:updateSspOsSoftware

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Request to upgrade software on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateSspOsSoftware)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-ssp-os-software-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateUpdateSspOsSoftware

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-local-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateWaitForAdaptorNwFwUpdateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-peer-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateWaitForAdaptorNwFwUpdatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:waitForIBMCFwUpdate

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForIBMCFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-foribmcfw-update-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateWaitForIBMCFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalAssociate:waitForSspOsUpdateComplete

Fault Code: F16973

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for upgrade complete from server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForSspOsUpdateComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-ssp-os-update-complete-failed

mibFaultCode: 16973

mibFaultName: fsmStFailComputePhysicalAssociateWaitForSspOsUpdateComplete

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BiosPostCompletion

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BmcConfigPnuOS

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BmcPreconfigPnuOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BmcPreconfigPnuOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BmcUnconfigPnuOS

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BootPnuos

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Bring-up pre-boot environment on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:BootWait

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:CheckPowerAvailability

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:ConfigBios

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configuring BIOS Defaults on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-bios-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateConfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:ConfigFlexFlashScrub

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configuring FlexFlash Scrub on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateConfigFlexFlashScrub

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:ConfigKvmMgmtDefaultSetting

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configure KVM Mgmt to default before ConfigPnuOs(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigKvmMgmtDefaultSetting)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-kvm-mgmt-default-setting-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateConfigKvmMgmtDefaultSetting

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:ConfigUserAccess

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateConfigUserAccess

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:DeassertResetBypass

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:HandlePooling

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Apply post-disassociation policies to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateHandlePooling

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicConfigPnuOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicConfigPnuOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigHostOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-hostoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigHostOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-hostospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigPnuOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigPnuOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigServiceInfraLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure service infra connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-service-infra-local-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:NicUnconfigServiceInfraPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure service infra connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-service-infra-peer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateNicUnconfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSCatalog

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSIdent

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSPolicy

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSScrub

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Scrub server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSScrub

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSSelfTest

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Trigger self-test of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSUnconfig

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure server from service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSUnconfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunconfig-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSUnconfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PnuOSValidate

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Pre-boot environment validate server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PowerDeployWait

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PowerOn

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Power on server for unconfiguration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:PreSanitize

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociatePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:ResetSecureBootConfig

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secure boot configuration(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ResetSecureBootConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-secure-boot-config-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateResetSecureBootConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:Sanitize

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:Shutdown

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SolRedirectDisable

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol redirection on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SolRedirectEnable

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token for server [serverId] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwConfigPnuOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwConfigPnuOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwConfigPortNivLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwConfigPortNivPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwUnconfigHostOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure host OS connectivity from server to primary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-hostoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwUnconfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwUnconfigHostOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure host OS connectivity from server to secondary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-hostospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwUnconfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwUnconfigPnuOSLocal

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:SwUnconfigPnuOSPeer

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigBios

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring BIOS Settings and Boot Order of server [serverId] (service profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-bios-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigCimcVMedia

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigExtMgmtGw

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigExtMgmtRules

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigFlexFlash

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigFlexFlash)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-flex-flash-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigFlexFlash

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigSoL

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Removing SoL configuration from server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigSoL)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-so-lfailed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:UnconfigUuid

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Restore original UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-uuid-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateUnconfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:VerifyFcZoneConfig

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:VerifyFcZoneConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-fc-zone-config-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateVerifyFcZoneConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:hagPnuOSConnect

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:hagPnuOSDisconnect

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:serialDebugPnuOSConnect

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDisassociate:serialDebugPnuOSDisconnect

Fault Code: F16974

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 16974

mibFaultName: fsmStFailComputePhysicalDisassociateSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalPowerCap:Config

Fault Code: F16975

Message

[FSM:STAGE:FAILED|RETRY]: Configuring power cap of server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowerCap:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 16975

mibFaultName: fsmStFailComputePhysicalPowerCapConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:CleanupCIMC

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning up CIMC configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupCIMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanupcimc-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionCleanupCIMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:CleanupPortConfigLocal

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning up local port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-port-config-local-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionCleanupPortConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:CleanupPortConfigPeer

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning up peer port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-port-config-peer-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionCleanupPortConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:Execute

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Decommissioning server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:StopVMediaLocal

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionStopVMediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:StopVMediaPeer

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionStopVMediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:UnconfigExtMgmtGw

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDecommission:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalDecommission:UnconfigExtMgmtRules

Fault Code: F16976

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDecommission:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 16976

mibFaultName: fsmStFailComputePhysicalDecommissionUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSoftShutdown:Execute

Fault Code: F16977

Message

[FSM:STAGE:FAILED|RETRY]: Soft shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftShutdown:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16977

mibFaultName: fsmStFailComputePhysicalSoftShutdownExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalHardShutdown:Execute

Fault Code: F16978

Message

[FSM:STAGE:FAILED|RETRY]: Hard shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardShutdown:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16978

mibFaultName: fsmStFailComputePhysicalHardShutdownExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalTurnup:Execute

Fault Code: F16979

Message

[FSM:STAGE:FAILED|RETRY]: Power-on server [dn](FSM-STAGE:sam:dme:ComputePhysicalTurnup:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16979

mibFaultName: fsmStFailComputePhysicalTurnupExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalPowercycle:Execute

Fault Code: F16980

Message

[FSM:STAGE:FAILED|RETRY]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16980

mibFaultName: fsmStFailComputePhysicalPowercycleExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalPowercycle:PreSanitize

Fault Code: F16980

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16980

mibFaultName: fsmStFailComputePhysicalPowercyclePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalPowercycle:Sanitize

Fault Code: F16980

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16980

mibFaultName: fsmStFailComputePhysicalPowercycleSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalHardreset:Execute

Fault Code: F16981

Message

[FSM:STAGE:FAILED|RETRY]: Hard-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16981

mibFaultName: fsmStFailComputePhysicalHardresetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalHardreset:PreSanitize

Fault Code: F16981

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16981

mibFaultName: fsmStFailComputePhysicalHardresetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalHardreset:Sanitize

Fault Code: F16981

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16981

mibFaultName: fsmStFailComputePhysicalHardresetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSoftreset:Execute

Fault Code: F16982

Message

[FSM:STAGE:FAILED|RETRY]: Soft-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16982

mibFaultName: fsmStFailComputePhysicalSoftresetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSoftreset:PreSanitize

Fault Code: F16982

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16982

mibFaultName: fsmStFailComputePhysicalSoftresetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSoftreset:Sanitize

Fault Code: F16982

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16982

mibFaultName: fsmStFailComputePhysicalSoftresetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSwConnUpd:A

Fault Code: F16983

Message

[FSM:STAGE:FAILED|RETRY]: Updating fabric A for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:A)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: a-failed

mibFaultCode: 16983

mibFaultName: fsmStFailComputePhysicalSwConnUpdA

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalSwConnUpd:B

Fault Code: F16983

Message

[FSM:STAGE:FAILED|RETRY]: Updating fabric B for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:B)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: b-failed

mibFaultCode: 16983

mibFaultName: fsmStFailComputePhysicalSwConnUpdB

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Cleanup

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Completing BIOS recovery mode for server [dn], and shutting it down(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Cleanup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryCleanup

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:PreSanitize

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Reset

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Resetting server [dn] power state after BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Sanitize

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoverySanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:SetupVmediaLocal

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:SetupVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-local-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoverySetupVmediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:SetupVmediaPeer

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:SetupVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-peer-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoverySetupVmediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Shutdown

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Shutting down server [dn] to prepare for BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Start

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Running BIOS recovery on server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryStart

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:StopVMediaLocal

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryStopVMediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:StopVMediaPeer

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryStopVMediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:TeardownVmediaLocal

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:TeardownVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-local-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryTeardownVmediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:TeardownVmediaPeer

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:TeardownVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-peer-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryTeardownVmediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalBiosRecovery:Wait

Fault Code: F16984

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for completion of BIOS recovery for server [dn] (up to 15 min)(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 16984

mibFaultName: fsmStFailComputePhysicalBiosRecoveryWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:BladePowerOn

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetBladePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:Execute

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Resetting CMOS for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:PreSanitize

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:ReconfigBios

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Reconfiguring BIOS Settings and Boot Order of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reconfig-bios-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetReconfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:ReconfigUuid

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Reconfiguring logical UUID of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reconfig-uuid-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetReconfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalCmosReset:Sanitize

Fault Code: F16986

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16986

mibFaultName: fsmStFailComputePhysicalCmosResetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalResetBmc:Execute

Fault Code: F16987

Message

[FSM:STAGE:FAILED|RETRY]: Resetting Management Controller on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetBmc:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16987

mibFaultName: fsmStFailComputePhysicalResetBmcExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailEquipmentIOCardResetIom:Execute

Fault Code: F16988

Message

[FSM:STAGE:FAILED|RETRY]: Reset IOM [id] on Fex [chassisId](FSM-STAGE:sam:dme:EquipmentIOCardResetIom:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 16988

mibFaultName: fsmStFailEquipmentIOCardResetIomExecute

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailComputeRackUnitDiscover:BiosPostCompletion

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBiosPostCompletion

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BladePowerOff

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: power on server [id] for discovery(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBladePowerOff

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcConfigPnuOS

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcConfigPnuOS

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcConfigureConnLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcConfigureConnLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcConfigureConnPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcConfigureConnPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcInventory

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: getting inventory of server [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcPreconfigPnuOSLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcPreconfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcPreconfigPnuOSPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcPreconfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcPresence

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: checking CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcPresence

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcShutdownDiscovered

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown the server [id]; deep discovery completed(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcShutdownDiscovered)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-discovered-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcShutdownDiscovered

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BmcUnconfigPnuOS

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the bootable device for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBmcUnconfigPnuOS

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BootPnuos

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: power server [id] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBootPnuos

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:BootWait

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverBootWait

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:ConfigDiscoveryMode

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: setting adapter mode to discovery for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigDiscoveryMode)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-discovery-mode-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverConfigDiscoveryMode

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:ConfigFlexFlashScrub

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Configuring FlexFlash Scrub on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverConfigFlexFlashScrub

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:ConfigNivMode

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: setting adapter mode to NIV for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigNivMode)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-niv-mode-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverConfigNivMode

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:ConfigUserAccess

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configuring external user access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverConfigUserAccess

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:HandlePooling

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Invoke post-discovery policies on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverHandlePooling

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:NicConfigPnuOSLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configure primary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverNicConfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:NicConfigPnuOSPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configure secondary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverNicConfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:NicInventoryLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicInventoryLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverNicInventoryLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:NicInventoryPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicInventoryPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverNicInventoryPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:OobStorageInventory

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: getting oob storage inventory of server [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverOobStorageInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSCatalog

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSCatalog

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSConnStatus

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconn-status-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSConnStatus

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSConnectivity

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconnectivity-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSConnectivity

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSIdent

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSIdent

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSInventory

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Perform inventory of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSPolicy

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSPolicy

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSScrub

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Scrub server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSScrub

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PnuOSSelfTest

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Trigger self-test of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPnuOSSelfTest

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:PreSanitize

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverPreSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:ReadSmbios

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for SMBIOS table from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: read-smbios-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverReadSmbios

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:Sanitize

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SolRedirectDisable

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSolRedirectDisable

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SolRedirectEnable

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token on server [id] for Sol redirect(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSolRedirectEnable

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigPnuOSLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigPnuOSPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigPortNivLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigPortNivLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigPortNivPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigPortNivPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigureConnLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigureConnLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwConfigureConnPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwConfigureConnPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwPnuOSConnectivityLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-pnuosconnectivity-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwPnuOSConnectivityLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwPnuOSConnectivityPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-pnuosconnectivity-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwPnuOSConnectivityPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwUnconfigPortNivLocal

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-port-niv-local-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwUnconfigPortNivLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:SwUnconfigPortNivPeer

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-port-niv-peer-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSwUnconfigPortNivPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:UnconfigCimcVMedia

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all bmc mappings for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverUnconfigCimcVMedia

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:UnconfigExtMgmtGw

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverUnconfigExtMgmtGw

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:UnconfigExtMgmtRules

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverUnconfigExtMgmtRules

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:hagConnect

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:hagConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-connect-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverHagConnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:hagDisconnect

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:hagDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-disconnect-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverHagDisconnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:serialDebugConnect

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSerialDebugConnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:serialDebugDisconnect

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverSerialDebugDisconnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitDiscover:waitForConnReady

Fault Code: F16994

Message

[FSM:STAGE:FAILED|RETRY]: wait for connection to be established(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:waitForConnReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-conn-ready-failed

mibFaultCode: 16994

mibFaultName: fsmStFailComputeRackUnitDiscoverWaitForConnReady

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailLsServerConfigure:AnalyzeImpact

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Analyzing changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: analyze-impact-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureAnalyzeImpact

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ApplyConfig

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Applying config to server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureApplyConfig

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ApplyDefaultIdentifiers

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving and applying default identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyDefaultIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-default-identifiers-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureApplyDefaultIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ApplyIdentifiers

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving and applying identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-identifiers-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureApplyIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ApplyPolicies

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving and applying policies(FSM-STAGE:sam:dme:LsServerConfigure:ApplyPolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-policies-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureApplyPolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ApplyTemplate

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Applying configuration template [srcTemplName](FSM-STAGE:sam:dme:LsServerConfigure:ApplyTemplate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-template-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureApplyTemplate

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:CommitStorage

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: committing storage for service profile(FSM-STAGE:sam:dme:LsServerConfigure:CommitStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: commit-storage-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureCommitStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:EvaluateAssociation

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Evaluate association with server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:EvaluateAssociation)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-association-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureEvaluateAssociation

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ProvisionStorage

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving storage policy(FSM-STAGE:sam:dme:LsServerConfigure:ProvisionStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: provision-storage-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureProvisionStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveBootConfig

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Computing binding changes(FSM-STAGE:sam:dme:LsServerConfigure:ResolveBootConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-boot-config-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveBootConfig

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveDefaultIdentifiers

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving default identifiers from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDefaultIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-default-identifiers-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveDefaultIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveDistributable

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveDistributable

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveDistributableNames

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving distributable names from host pack(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveDistributableNames

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveIdentifiers

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving identifiers from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-identifiers-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveImages

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveImages

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveNetworkPolicies

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving various dependent policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkPolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-network-policies-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveNetworkPolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveNetworkTemplates

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving various template policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkTemplates)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-network-templates-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveNetworkTemplates

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolvePolicies

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving various policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolvePolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-policies-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolvePolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ResolveSchedule

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Resolving schedule policy from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveSchedule)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-schedule-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureResolveSchedule

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:ValidatePolicyOwnership

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Validating policy integrity from ownership perspective(FSM-STAGE:sam:dme:LsServerConfigure:ValidatePolicyOwnership)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-policy-ownership-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureValidatePolicyOwnership

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:WaitForAssocCompletion

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Association completion on server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:WaitForAssocCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-assoc-completion-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureWaitForAssocCompletion

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:WaitForCommitStorage

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for storage commit to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForCommitStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-commit-storage-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureWaitForCommitStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:WaitForMaintPermission

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for ack or maint window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintPermission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-maint-permission-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureWaitForMaintPermission

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:WaitForMaintWindow

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for maintenance window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintWindow)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-maint-window-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureWaitForMaintWindow

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:WaitForStorageProvision

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: waiting for storage provisioning to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForStorageProvision)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-storage-provision-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureWaitForStorageProvision

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:checkAssignedDefaultIdentifiersForDup

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: checking assigned identifiers(from default pool) for dup(FSM-STAGE:sam:dme:LsServerConfigure:checkAssignedDefaultIdentifiersForDup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-assigned-default-identifiers-for-dup-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureCheckAssignedDefaultIdentifiersForDup

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailLsServerConfigure:checkAssignedIdentifiersForDup

Fault Code: F16995

Message

[FSM:STAGE:FAILED|RETRY]: checking assigned identifiers for dup(FSM-STAGE:sam:dme:LsServerConfigure:checkAssignedIdentifiersForDup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-assigned-identifiers-for-dup-failed

mibFaultCode: 16995

mibFaultName: fsmStFailLsServerConfigureCheckAssignedIdentifiersForDup

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmStFailSwEthMonDeploy:UpdateEthMon

Fault Code: F17000

Message

[FSM:STAGE:FAILED|RETRY]: Ethernet traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwEthMonDeploy:UpdateEthMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-eth-mon-failed

mibFaultCode: 17000

mibFaultName: fsmStFailSwEthMonDeployUpdateEthMon

moClass: sw:EthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]

fsmStFailSwFcMonDeploy:UpdateFcMon

Fault Code: F17001

Message

[FSM:STAGE:FAILED|RETRY]: FC traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwFcMonDeploy:UpdateFcMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-fc-mon-failed

mibFaultCode: 17001

mibFaultName: fsmStFailSwFcMonDeployUpdateFcMon

moClass: sw:FcMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]

fsmStFailFabricSanCloudSwitchMode:SwConfigLocal

Fault Code: F17002

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:FabricSanCloudSwitchMode:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 17002

mibFaultName: fsmStFailFabricSanCloudSwitchModeSwConfigLocal

moClass: fabric:SanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/san

fsmStFailFabricSanCloudSwitchMode:SwConfigPeer

Fault Code: F17002

Message

[FSM:STAGE:FAILED|RETRY]: Fabric interconnect FC mode configuration to primary(FSM-STAGE:sam:dme:FabricSanCloudSwitchMode:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 17002

mibFaultName: fsmStFailFabricSanCloudSwitchModeSwConfigPeer

moClass: fabric:SanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/san

fsmStFailComputePhysicalUpdateExtUsers:Deploy

Fault Code: F17008

Message

[FSM:STAGE:FAILED|RETRY]: external mgmt user deployment on server [dn] (profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalUpdateExtUsers:Deploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deploy-failed

mibFaultCode: 17008

mibFaultName: fsmStFailComputePhysicalUpdateExtUsersDeploy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailSysdebugTechSupportInitiate:Local

Fault Code: F17012

Message

[FSM:STAGE:FAILED|RETRY]: create tech-support file from GUI on local(FSM-STAGE:sam:dme:SysdebugTechSupportInitiate:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17012

mibFaultName: fsmStFailSysdebugTechSupportInitiateLocal

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDeleteTechSupFile:Local

Fault Code: F17013

Message

[FSM:STAGE:FAILED|RETRY]: delete tech-support file from GUI on local(FSM-STAGE:sam:dme:SysdebugTechSupportDeleteTechSupFile:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17013

mibFaultName: fsmStFailSysdebugTechSupportDeleteTechSupFileLocal

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDeleteTechSupFile:peer

Fault Code: F17013

Message

[FSM:STAGE:FAILED|RETRY]: delete tech-support file from GUI on peer(FSM-STAGE:sam:dme:SysdebugTechSupportDeleteTechSupFile:peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 17013

mibFaultName: fsmStFailSysdebugTechSupportDeleteTechSupFilePeer

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDownload:CopyPrimary

Fault Code: F17014

Message

[FSM:STAGE:FAILED|RETRY]: Copy the tech-support file to primary for download(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:CopyPrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-primary-failed

mibFaultCode: 17014

mibFaultName: fsmStFailSysdebugTechSupportDownloadCopyPrimary

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDownload:CopySub

Fault Code: F17014

Message

[FSM:STAGE:FAILED|RETRY]: copy tech-support file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:CopySub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-sub-failed

mibFaultCode: 17014

mibFaultName: fsmStFailSysdebugTechSupportDownloadCopySub

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDownload:DeletePrimary

Fault Code: F17014

Message

[FSM:STAGE:FAILED|RETRY]: Delete the tech-support file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:DeletePrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-primary-failed

mibFaultCode: 17014

mibFaultName: fsmStFailSysdebugTechSupportDownloadDeletePrimary

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailSysdebugTechSupportDownload:DeleteSub

Fault Code: F17014

Message

[FSM:STAGE:FAILED|RETRY]: Delete the tech-support file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:DeleteSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-sub-failed

mibFaultCode: 17014

mibFaultName: fsmStFailSysdebugTechSupportDownloadDeleteSub

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmStFailComputePhysicalUpdateAdaptor:CheckPowerAvailability

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:PollUpdateStatusLocal

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-local-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorPollUpdateStatusLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:PollUpdateStatusPeer

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-peer-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorPollUpdateStatusPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:PowerDeployWait

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorPowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:PowerOff

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-off-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:PowerOn

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:UpdateRequestLocal

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-local-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorUpdateRequestLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateAdaptor:UpdateRequestPeer

Fault Code: F17043

Message

[FSM:STAGE:FAILED|RETRY]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-peer-failed

mibFaultCode: 17043

mibFaultName: fsmStFailComputePhysicalUpdateAdaptorUpdateRequestPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:ActivateLocal

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-local-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorActivateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:ActivatePeer

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-peer-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorActivatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:CheckPowerAvailability

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:DeassertResetBypass

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:PowerDeployWait

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorPowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:PowerOn

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateAdaptor:Reset

Fault Code: F17044

Message

[FSM:STAGE:FAILED|RETRY]: reseting the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 17044

mibFaultName: fsmStFailComputePhysicalActivateAdaptorReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailCapabilityCatalogueActivateCatalog:ApplyCatalog

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:ApplyCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-catalog-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogApplyCatalog

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:CopyCatFromRep

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: Copying Catalogue from repository to FI(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyCatFromRep)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-cat-from-rep-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogCopyCatFromRep

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:CopyExternalRepToRemote

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: syncing external repository to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyExternalRepToRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-external-rep-to-remote-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogCopyExternalRepToRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:CopyRemote

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: syncing catalog changes to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogCopyRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:EvaluateStatus

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogEvaluateStatus

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:RescanImages

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: rescanning image files(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogRescanImages

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityCatalogueActivateCatalog:UnpackLocal

Fault Code: F17045

Message

[FSM:STAGE:FAILED|RETRY]: activating catalog changes(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 17045

mibFaultName: fsmStFailCapabilityCatalogueActivateCatalogUnpackLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmStFailCapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog

Fault Code: F17046

Message

[FSM:STAGE:FAILED|RETRY]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-catalog-failed

mibFaultCode: 17046

mibFaultName: fsmStFailCapabilityMgmtExtensionActivateMgmtExtApplyCatalog

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmStFailCapabilityMgmtExtensionActivateMgmtExt:CopyRemote

Fault Code: F17046

Message

[FSM:STAGE:FAILED|RETRY]: syncing management extension changes to subordinate(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 17046

mibFaultName: fsmStFailCapabilityMgmtExtensionActivateMgmtExtCopyRemote

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmStFailCapabilityMgmtExtensionActivateMgmtExt:EvaluateStatus

Fault Code: F17046

Message

[FSM:STAGE:FAILED|RETRY]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 17046

mibFaultName: fsmStFailCapabilityMgmtExtensionActivateMgmtExtEvaluateStatus

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmStFailCapabilityMgmtExtensionActivateMgmtExt:RescanImages

Fault Code: F17046

Message

[FSM:STAGE:FAILED|RETRY]: rescanning image files(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 17046

mibFaultName: fsmStFailCapabilityMgmtExtensionActivateMgmtExtRescanImages

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmStFailCapabilityMgmtExtensionActivateMgmtExt:UnpackLocal

Fault Code: F17046

Message

[FSM:STAGE:FAILED|RETRY]: activating management extension changes(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 17046

mibFaultName: fsmStFailCapabilityMgmtExtensionActivateMgmtExtUnpackLocal

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmStFailLicenseDownloaderDownload:CopyRemote

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: Copy the license file to subordinate for inventory(FSM-STAGE:sam:dme:LicenseDownloaderDownload:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadCopyRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseDownloaderDownload:DeleteLocal

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: deleting temporary files for [fileName] on local(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadDeleteLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseDownloaderDownload:DeleteRemote

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: deleting temporary files for [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-remote-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadDeleteRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseDownloaderDownload:Local

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: downloading license file [fileName] from [server](FSM-STAGE:sam:dme:LicenseDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseDownloaderDownload:ValidateLocal

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: validation for license file [fileName] on primary(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-local-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadValidateLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseDownloaderDownload:ValidateRemote

Fault Code: F17050

Message

[FSM:STAGE:FAILED|RETRY]: validation for license file [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-remote-failed

mibFaultCode: 17050

mibFaultName: fsmStFailLicenseDownloaderDownloadValidateRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmStFailLicenseFileInstall:Local

Fault Code: F17051

Message

[FSM:STAGE:FAILED|RETRY]: Installing license on primary(FSM-STAGE:sam:dme:LicenseFileInstall:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17051

mibFaultName: fsmStFailLicenseFileInstallLocal

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmStFailLicenseFileInstall:Remote

Fault Code: F17051

Message

[FSM:STAGE:FAILED|RETRY]: Installing license on subordinate(FSM-STAGE:sam:dme:LicenseFileInstall:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 17051

mibFaultName: fsmStFailLicenseFileInstallRemote

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmStFailLicenseFileClear:Local

Fault Code: F17052

Message

[FSM:STAGE:FAILED|RETRY]: Clearing license on primary(FSM-STAGE:sam:dme:LicenseFileClear:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17052

mibFaultName: fsmStFailLicenseFileClearLocal

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmStFailLicenseFileClear:Remote

Fault Code: F17052

Message

[FSM:STAGE:FAILED|RETRY]: Clearing license on subordinate(FSM-STAGE:sam:dme:LicenseFileClear:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 17052

mibFaultName: fsmStFailLicenseFileClearRemote

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmStFailLicenseInstanceUpdateFlexlm:Local

Fault Code: F17053

Message

[FSM:STAGE:FAILED|RETRY]: Updating on primary(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17053

mibFaultName: fsmStFailLicenseInstanceUpdateFlexlmLocal

moClass: license:Instance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fsmStFailLicenseInstanceUpdateFlexlm:Remote

Fault Code: F17053

Message

[FSM:STAGE:FAILED|RETRY]: Updating on subordinate(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 17053

mibFaultName: fsmStFailLicenseInstanceUpdateFlexlmRemote

moClass: license:Instance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fsmStFailComputePhysicalConfigSoL:Execute

Fault Code: F17083

Message

[FSM:STAGE:FAILED|RETRY]: configuring SoL interface on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigSoL:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17083

mibFaultName: fsmStFailComputePhysicalConfigSoLExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUnconfigSoL:Execute

Fault Code: F17084

Message

[FSM:STAGE:FAILED|RETRY]: removing SoL interface configuration from server [dn](FSM-STAGE:sam:dme:ComputePhysicalUnconfigSoL:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17084

mibFaultName: fsmStFailComputePhysicalUnconfigSoLExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailPortPIoInCompatSfpPresence:Shutdown

Fault Code: F17089

Message

[FSM:STAGE:FAILED|RETRY]: Shutting down port(FSM-STAGE:sam:dme:PortPIoInCompatSfpPresence:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 17089

mibFaultName: fsmStFailPortPIoInCompatSfpPresenceShutdown

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmStFailComputePhysicalDiagnosticInterrupt:Execute

Fault Code: F17116

Message

[FSM:STAGE:FAILED|RETRY]: Execute Diagnostic Interrupt(NMI) for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDiagnosticInterrupt:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17116

mibFaultName: fsmStFailComputePhysicalDiagnosticInterruptExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailSysdebugCoreDownload:CopyPrimary

Fault Code: F17133

Message

[FSM:STAGE:FAILED|RETRY]: Copy the Core file to primary for download(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopyPrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-primary-failed

mibFaultCode: 17133

mibFaultName: fsmStFailSysdebugCoreDownloadCopyPrimary

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmStFailSysdebugCoreDownload:CopySub

Fault Code: F17133

Message

[FSM:STAGE:FAILED|RETRY]: copy Core file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopySub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-sub-failed

mibFaultCode: 17133

mibFaultName: fsmStFailSysdebugCoreDownloadCopySub

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmStFailSysdebugCoreDownload:DeletePrimary

Fault Code: F17133

Message

[FSM:STAGE:FAILED|RETRY]: Delete the Core file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeletePrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-primary-failed

mibFaultCode: 17133

mibFaultName: fsmStFailSysdebugCoreDownloadDeletePrimary

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmStFailSysdebugCoreDownload:DeleteSub

Fault Code: F17133

Message

[FSM:STAGE:FAILED|RETRY]: Delete the Core file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeleteSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-sub-failed

mibFaultCode: 17133

mibFaultName: fsmStFailSysdebugCoreDownloadDeleteSub

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmStFailEquipmentChassisDynamicReallocation:Config

Fault Code: F17134

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:EquipmentChassisDynamicReallocation:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 17134

mibFaultName: fsmStFailEquipmentChassisDynamicReallocationConfig

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailComputePhysicalResetKvm:Execute

Fault Code: F17163

Message

[FSM:STAGE:FAILED|RETRY]: Execute KVM Reset for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetKvm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17163

mibFaultName: fsmStFailComputePhysicalResetKvmExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailMgmtControllerOnline:BmcConfigureConnLocal

Fault Code: F17169

Message

[FSM:STAGE:FAILED|RETRY]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-local-failed

mibFaultCode: 17169

mibFaultName: fsmStFailMgmtControllerOnlineBmcConfigureConnLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerOnline:BmcConfigureConnPeer

Fault Code: F17169

Message

[FSM:STAGE:FAILED|RETRY]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-peer-failed

mibFaultCode: 17169

mibFaultName: fsmStFailMgmtControllerOnlineBmcConfigureConnPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerOnline:SwConfigureConnLocal

Fault Code: F17169

Message

[FSM:STAGE:FAILED|RETRY]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-local-failed

mibFaultCode: 17169

mibFaultName: fsmStFailMgmtControllerOnlineSwConfigureConnLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerOnline:SwConfigureConnPeer

Fault Code: F17169

Message

[FSM:STAGE:FAILED|RETRY]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-peer-failed

mibFaultCode: 17169

mibFaultName: fsmStFailMgmtControllerOnlineSwConfigureConnPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailComputeRackUnitOffline:CleanupLocal

Fault Code: F17170

Message

[FSM:STAGE:FAILED|RETRY]: cleaning host entries on local fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-local-failed

mibFaultCode: 17170

mibFaultName: fsmStFailComputeRackUnitOfflineCleanupLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitOffline:CleanupPeer

Fault Code: F17170

Message

[FSM:STAGE:FAILED|RETRY]: cleaning host entries on peer fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-peer-failed

mibFaultCode: 17170

mibFaultName: fsmStFailComputeRackUnitOfflineCleanupPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitOffline:SwUnconfigureLocal

Fault Code: F17170

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigureLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfigure-local-failed

mibFaultCode: 17170

mibFaultName: fsmStFailComputeRackUnitOfflineSwUnconfigureLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitOffline:SwUnconfigurePeer

Fault Code: F17170

Message

[FSM:STAGE:FAILED|RETRY]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigurePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfigure-peer-failed

mibFaultCode: 17170

mibFaultName: fsmStFailComputeRackUnitOfflineSwUnconfigurePeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailEquipmentLocatorLedSetFiLocatorLed:Execute

Fault Code: F17187

Message

[FSM:STAGE:FAILED|RETRY]: setting FI locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFiLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17187

mibFaultName: fsmStFailEquipmentLocatorLedSetFiLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmStFailFabricEpMgrConfigure:ApplyConfig

Fault Code: F17214

Message

[FSM:STAGE:FAILED|RETRY]: Apply switch configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 17214

mibFaultName: fsmStFailFabricEpMgrConfigureApplyConfig

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmStFailFabricEpMgrConfigure:ApplyPhysical

Fault Code: F17214

Message

[FSM:STAGE:FAILED|RETRY]: Applying physical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyPhysical)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-physical-failed

mibFaultCode: 17214

mibFaultName: fsmStFailFabricEpMgrConfigureApplyPhysical

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmStFailFabricEpMgrConfigure:ValidateConfiguration

Fault Code: F17214

Message

[FSM:STAGE:FAILED|RETRY]: Validating logical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ValidateConfiguration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-configuration-failed

mibFaultCode: 17214

mibFaultName: fsmStFailFabricEpMgrConfigureValidateConfiguration

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmStFailFabricEpMgrConfigure:WaitOnPhys

Fault Code: F17214

Message

[FSM:STAGE:FAILED|RETRY]: Waiting on physical change application(FSM-STAGE:sam:dme:FabricEpMgrConfigure:WaitOnPhys)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-on-phys-failed

mibFaultCode: 17214

mibFaultName: fsmStFailFabricEpMgrConfigureWaitOnPhys

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmStFailVnicProfileSetDeployAlias:Local

Fault Code: F17223

Message

[FSM:STAGE:FAILED|RETRY]: VNIC profile alias configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17223

mibFaultName: fsmStFailVnicProfileSetDeployAliasLocal

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmStFailVnicProfileSetDeployAlias:Peer

Fault Code: F17223

Message

[FSM:STAGE:FAILED|RETRY]: VNIC profile alias configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 17223

mibFaultName: fsmStFailVnicProfileSetDeployAliasPeer

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmStFailSwPhysConfPhysical:ConfigSwA

Fault Code: F17239

Message

[FSM:STAGE:FAILED|RETRY]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-afailed

mibFaultCode: 17239

mibFaultName: fsmStFailSwPhysConfPhysicalConfigSwA

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmStFailSwPhysConfPhysical:ConfigSwB

Fault Code: F17239

Message

[FSM:STAGE:FAILED|RETRY]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-bfailed

mibFaultCode: 17239

mibFaultName: fsmStFailSwPhysConfPhysicalConfigSwB

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmStFailSwPhysConfPhysical:PortInventorySwA

Fault Code: F17239

Message

[FSM:STAGE:FAILED|RETRY]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-afailed

mibFaultCode: 17239

mibFaultName: fsmStFailSwPhysConfPhysicalPortInventorySwA

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmStFailSwPhysConfPhysical:PortInventorySwB

Fault Code: F17239

Message

[FSM:STAGE:FAILED|RETRY]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-bfailed

mibFaultCode: 17239

mibFaultName: fsmStFailSwPhysConfPhysicalPortInventorySwB

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmStFailSwPhysConfPhysical:VerifyPhysConfig

Fault Code: F17239

Message

[FSM:STAGE:FAILED|RETRY]: Verifying physical transition on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:VerifyPhysConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-phys-config-failed

mibFaultCode: 17239

mibFaultName: fsmStFailSwPhysConfPhysicalVerifyPhysConfig

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmStFailExtvmmEpClusterRole:SetLocal

Fault Code: F17254

Message

[FSM:STAGE:FAILED|RETRY]: external VM management cluster role configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 17254

mibFaultName: fsmStFailExtvmmEpClusterRoleSetLocal

moClass: extvmm:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt

fsmStFailExtvmmEpClusterRole:SetPeer

Fault Code: F17254

Message

[FSM:STAGE:FAILED|RETRY]: external VM management cluster role configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 17254

mibFaultName: fsmStFailExtvmmEpClusterRoleSetPeer

moClass: extvmm:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt

fsmStFailVmLifeCyclePolicyConfig:Local

Fault Code: F17259

Message

[FSM:STAGE:FAILED|RETRY]: set Veth Auto-delete Retention Timer on local fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17259

mibFaultName: fsmStFailVmLifeCyclePolicyConfigLocal

moClass: vm:LifeCyclePolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vm-lc-policy

fsmStFailVmLifeCyclePolicyConfig:Peer

Fault Code: F17259

Message

[FSM:STAGE:FAILED|RETRY]: set Veth Auto-delete Retention Timer on peer fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 17259

mibFaultName: fsmStFailVmLifeCyclePolicyConfigPeer

moClass: vm:LifeCyclePolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vm-lc-policy

fsmStFailEquipmentBeaconLedIlluminate:ExecuteA

Fault Code: F17262

Message

[FSM:STAGE:FAILED|RETRY]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-afailed

mibFaultCode: 17262

mibFaultName: fsmStFailEquipmentBeaconLedIlluminateExecuteA

moClass: equipment:BeaconLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/beacon

Affected MO: sys/chassis-[id]/blade-[slotId]/beacon

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/chassis-[id]/psu-[id]/beacon

Affected MO: sys/chassis-[id]/slot-[id]/beacon

Affected MO: sys/fex-[id]/beacon

Affected MO: sys/fex-[id]/psu-[id]/beacon

Affected MO: sys/fex-[id]/slot-[id]/beacon

Affected MO: sys/rack-unit-[id]/beacon

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/rack-unit-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/switch-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/slot-[id]/beacon

fsmStFailEquipmentBeaconLedIlluminate:ExecuteB

Fault Code: F17262

Message

[FSM:STAGE:FAILED|RETRY]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-bfailed

mibFaultCode: 17262

mibFaultName: fsmStFailEquipmentBeaconLedIlluminateExecuteB

moClass: equipment:BeaconLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/beacon

Affected MO: sys/chassis-[id]/blade-[slotId]/beacon

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/chassis-[id]/psu-[id]/beacon

Affected MO: sys/chassis-[id]/slot-[id]/beacon

Affected MO: sys/fex-[id]/beacon

Affected MO: sys/fex-[id]/psu-[id]/beacon

Affected MO: sys/fex-[id]/slot-[id]/beacon

Affected MO: sys/rack-unit-[id]/beacon

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/rack-unit-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/switch-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/slot-[id]/beacon

fsmStFailEtherServerIntFIoConfigSpeed:Configure

Fault Code: F17271

Message

[FSM:STAGE:FAILED|RETRY]: Configure admin speed for [dn](FSM-STAGE:sam:dme:EtherServerIntFIoConfigSpeed:Configure)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-failed

mibFaultCode: 17271

mibFaultName: fsmStFailEtherServerIntFIoConfigSpeedConfigure

moClass: ether:ServerIntFIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/rack-unit-[id]/diag/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmStFailComputePhysicalUpdateBIOS:Clear

Fault Code: F17281

Message

[FSM:STAGE:FAILED|RETRY]: clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:Clear)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-failed

mibFaultCode: 17281

mibFaultName: fsmStFailComputePhysicalUpdateBIOSClear

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBIOS:PollClearStatus

Fault Code: F17281

Message

[FSM:STAGE:FAILED|RETRY]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:PollClearStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-status-failed

mibFaultCode: 17281

mibFaultName: fsmStFailComputePhysicalUpdateBIOSPollClearStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBIOS:PollUpdateStatus

Fault Code: F17281

Message

[FSM:STAGE:FAILED|RETRY]: waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 17281

mibFaultName: fsmStFailComputePhysicalUpdateBIOSPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBIOS:UpdateRequest

Fault Code: F17281

Message

[FSM:STAGE:FAILED|RETRY]: sending BIOS update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 17281

mibFaultName: fsmStFailComputePhysicalUpdateBIOSUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:Activate

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: activating BIOS image(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSActivate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:Clear

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: clearing pending BIOS image activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Clear)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSClear

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:PollActivateStatus

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-status-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSPollActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:PollClearStatus

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: waiting for pending BIOS image activate to clear(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollClearStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-status-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSPollClearStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:PowerOff

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-off-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:PowerOn

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: power on the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalActivateBIOS:UpdateTokens

Fault Code: F17282

Message

[FSM:STAGE:FAILED|RETRY]: updating BIOS tokens(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:UpdateTokens)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-tokens-failed

mibFaultCode: 17282

mibFaultName: fsmStFailComputePhysicalActivateBIOSUpdateTokens

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailIdentIdentRequestUpdateIdent:Execute

Fault Code: F17312

Message

[FSM:STAGE:FAILED|RETRY]: Update identities to external identifier manager(FSM-STAGE:sam:dme:IdentIdentRequestUpdateIdent:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17312

mibFaultName: fsmStFailIdentIdentRequestUpdateIdentExecute

moClass: ident:IdentRequest

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys/IdentQ-[id]

fsmStFailIdentMetaSystemSync:Execute

Fault Code: F17313

Message

[FSM:STAGE:FAILED|RETRY]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17313

mibFaultName: fsmStFailIdentMetaSystemSyncExecute

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmStFailIdentMetaSystemSync:Ping

Fault Code: F17313

Message

[FSM:STAGE:FAILED|RETRY]: Check identifier manager availability(FSM-STAGE:sam:dme:IdentMetaSystemSync:Ping)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: ping-failed

mibFaultCode: 17313

mibFaultName: fsmStFailIdentMetaSystemSyncPing

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmStFailComputePhysicalResetIpmi:Execute

Fault Code: F17326

Message

[FSM:STAGE:FAILED|RETRY]: Execute Reset IPMI configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetIpmi:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17326

mibFaultName: fsmStFailComputePhysicalResetIpmiExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:ActivateBios

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:ActivateBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-bios-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeActivateBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BiosImgUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BiosImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-img-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBiosImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BiosPostCompletion

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BladePowerOff

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Power off server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBladePowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BmcConfigPnuOS

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BmcPreconfigPnuOSLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BmcPreconfigPnuOSPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BmcUnconfigPnuOS

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BootPnuos

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Bring-up pre-boot environment for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:BootWait

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:CheckPowerAvailability

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:ClearBiosUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:ClearBiosUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-bios-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeClearBiosUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:DeassertResetBypass

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:DeleteCurlDownloadedImages

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Delete images downloaded from operations manager(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:DeleteCurlDownloadedImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-curl-downloaded-images-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeDeleteCurlDownloadedImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:GraphicsImageUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update gpu firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:GraphicsImageUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: graphics-image-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeGraphicsImageUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:HbaImgUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:HbaImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hba-img-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeHbaImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:LocalDiskFwUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:LocalDiskFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-disk-fw-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeLocalDiskFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:NicConfigPnuOSLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:NicConfigPnuOSPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:NicImgUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-img-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeNicImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:NicUnconfigPnuOSLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:NicUnconfigPnuOSPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSCatalog

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSConfig

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconfig-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSIdent

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSInventory

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSPolicy

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSSelfTest

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSUnloadDrivers

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Unload drivers on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSUnloadDrivers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunload-drivers-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSUnloadDrivers

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PnuOSValidate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Pre-boot environment validation for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PollBiosActivateStatus

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBiosActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-activate-status-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePollBiosActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PollBiosUpdateStatus

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-update-status-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePollBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PollBoardCtrlUpdateStatus

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBoardCtrlUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-board-ctrl-update-status-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePollBoardCtrlUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PollClearBiosUpdateStatus

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollClearBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-bios-update-status-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePollClearBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PowerDeployWait

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PowerOn

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Power on server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:PreSanitize

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:Sanitize

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:Shutdown

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Shutting down server [dn] after firmware upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SolRedirectDisable

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Disable Sol redirection on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SolRedirectEnable

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: set up bios token for server for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:StorageCtlrImgUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:StorageCtlrImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: storage-ctlr-img-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeStorageCtlrImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwConfigPnuOSLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwConfigPnuOSPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwConfigPortNivLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwConfigPortNivPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwUnconfigPnuOSLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:SwUnconfigPnuOSPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:UnconfigCimcVMedia

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:UnconfigExtMgmtGw

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:UnconfigExtMgmtRules

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:UpdateBiosRequest

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBiosRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bios-request-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUpdateBiosRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:UpdateBoardCtrlRequest

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBoardCtrlRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-board-ctrl-request-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUpdateBoardCtrlRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:activateAdaptorNwFwLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-local-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeActivateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:activateAdaptorNwFwPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-peer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeActivateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:activateIBMCFw

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateibmcfw-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeActivateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:copyRemote

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Copy images to peer node(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:copyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeCopyRemote

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:downloadImages

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Download images from operations manager(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:downloadImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-images-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeDownloadImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:hagPnuOSConnect

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:hagPnuOSDisconnect

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:resetIBMC

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:resetIBMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resetibmc-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeResetIBMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:serialDebugPnuOSConnect

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:updateAdaptorNwFwLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-local-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUpdateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:updateAdaptorNwFwPeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-peer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUpdateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:updateIBMCFw

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateibmcfw-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeUpdateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-local-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeWaitForAdaptorNwFwUpdateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-peer-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeWaitForAdaptorNwFwUpdatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalFwUpgrade:waitForIBMCFwUpdate

Fault Code: F17327

Message

[FSM:STAGE:FAILED|RETRY]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForIBMCFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-foribmcfw-update-failed

mibFaultCode: 17327

mibFaultName: fsmStFailComputePhysicalFwUpgradeWaitForIBMCFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitAdapterReset:DeassertResetBypass

Fault Code: F17328

Message

[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 17328

mibFaultName: fsmStFailComputeRackUnitAdapterResetDeassertResetBypass

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitAdapterReset:PowerCycle

Fault Code: F17328

Message

[FSM:STAGE:FAILED|RETRY]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PowerCycle)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-cycle-failed

mibFaultCode: 17328

mibFaultName: fsmStFailComputeRackUnitAdapterResetPowerCycle

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitAdapterReset:PreSanitize

Fault Code: F17328

Message

[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 17328

mibFaultName: fsmStFailComputeRackUnitAdapterResetPreSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitAdapterReset:Sanitize

Fault Code: F17328

Message

[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 17328

mibFaultName: fsmStFailComputeRackUnitAdapterResetSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailPortPIoInCompatSfpReplaced:EnablePort

Fault Code: F17358

Message

[FSM:STAGE:FAILED|RETRY]: Enabling port(FSM-STAGE:sam:dme:PortPIoInCompatSfpReplaced:EnablePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-port-failed

mibFaultCode: 17358

mibFaultName: fsmStFailPortPIoInCompatSfpReplacedEnablePort

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmStFailExtpolEpRegisterFsm:Execute

Fault Code: F17359

Message

[FSM:STAGE:FAILED|RETRY]: Register FSM Execute(FSM-STAGE:sam:dme:ExtpolEpRegisterFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17359

mibFaultName: fsmStFailExtpolEpRegisterFsmExecute

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailExtpolRegistryCrossDomainConfig:SetLocal

Fault Code: F17360

Message

[FSM:STAGE:FAILED|RETRY]: Configure cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 17360

mibFaultName: fsmStFailExtpolRegistryCrossDomainConfigSetLocal

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmStFailExtpolRegistryCrossDomainConfig:SetPeer

Fault Code: F17360

Message

[FSM:STAGE:FAILED|RETRY]: Configure cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 17360

mibFaultName: fsmStFailExtpolRegistryCrossDomainConfigSetPeer

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmStFailExtpolRegistryCrossDomainDelete:SetLocal

Fault Code: F17361

Message

[FSM:STAGE:FAILED|RETRY]: Remove cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 17361

mibFaultName: fsmStFailExtpolRegistryCrossDomainDeleteSetLocal

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmStFailExtpolRegistryCrossDomainDelete:SetPeer

Fault Code: F17361

Message

[FSM:STAGE:FAILED|RETRY]: Remove cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 17361

mibFaultName: fsmStFailExtpolRegistryCrossDomainDeleteSetPeer

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmStFailNfsMountInstMount:MountLocal

Fault Code: F17377

Message

[FSM:STAGE:FAILED|RETRY]: Mount nfs [remoteDir] from server [server] on local switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mount-local-failed

mibFaultCode: 17377

mibFaultName: fsmStFailNfsMountInstMountMountLocal

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountInstMount:MountPeer

Fault Code: F17377

Message

[FSM:STAGE:FAILED|RETRY]: Mount nfs [remoteDir] from NFS server [server] on peer switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mount-peer-failed

mibFaultCode: 17377

mibFaultName: fsmStFailNfsMountInstMountMountPeer

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountInstMount:RegisterClient

Fault Code: F17377

Message

[FSM:STAGE:FAILED|RETRY]: Register client with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:RegisterClient)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: register-client-failed

mibFaultCode: 17377

mibFaultName: fsmStFailNfsMountInstMountRegisterClient

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountInstMount:VerifyRegistration

Fault Code: F17377

Message

[FSM:STAGE:FAILED|RETRY]: Verify client registration with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:VerifyRegistration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-registration-failed

mibFaultCode: 17377

mibFaultName: fsmStFailNfsMountInstMountVerifyRegistration

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountInstUnmount:UnmountLocal

Fault Code: F17378

Message

[FSM:STAGE:FAILED|RETRY]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unmount-local-failed

mibFaultCode: 17378

mibFaultName: fsmStFailNfsMountInstUnmountUnmountLocal

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountInstUnmount:UnmountPeer

Fault Code: F17378

Message

[FSM:STAGE:FAILED|RETRY]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unmount-peer-failed

mibFaultCode: 17378

mibFaultName: fsmStFailNfsMountInstUnmountUnmountPeer

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmStFailNfsMountDefReportNfsMountSuspend:Report

Fault Code: F17379

Message

[FSM:STAGE:FAILED|RETRY]: Report mount suspend success to operations manager(FSM-STAGE:sam:dme:NfsMountDefReportNfsMountSuspend:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 17379

mibFaultName: fsmStFailNfsMountDefReportNfsMountSuspendReport

moClass: nfs:MountDef

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: nfs-ep/nfs-mount-def-[name]

fsmStFailStorageSystemSync:Execute

Fault Code: F17395

Message

[FSM:STAGE:FAILED|RETRY]: Synchronise requestors with storage broker(FSM-STAGE:sam:dme:StorageSystemSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17395

mibFaultName: fsmStFailStorageSystemSyncExecute

moClass: storage:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: storage-ep/system

fsmStFailFirmwareSystemDeploy:ActivateIOM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Activating IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateiom-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployActivateIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ActivateLocalFI

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Activating Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateLocalFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-localfi-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployActivateLocalFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ActivateMgmtExt

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Activating MgmtExt(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateMgmtExt)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-mgmt-ext-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployActivateMgmtExt

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ActivateRemoteFI

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Activating Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateRemoteFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-remotefi-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployActivateRemoteFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ActivateUCSM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Activating FPRM(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateUCSM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateucsm-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployActivateUCSM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:DebundlePort

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Debundle the ports(FSM-STAGE:sam:dme:FirmwareSystemDeploy:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployDebundlePort

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollActivateOfIOM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Activation to complete on IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-ofiom-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollActivateOfIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollActivateOfLocalFI

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Activation to complete on Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfLocalFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-localfi-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollActivateOfLocalFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollActivateOfMgmtExt

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for MgmtExt Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfMgmtExt)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-mgmt-ext-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollActivateOfMgmtExt

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollActivateOfRemoteFI

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Activation to complete on Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfRemoteFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-remotefi-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollActivateOfRemoteFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollActivateOfUCSM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for FPRM Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfUCSM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-ofucsm-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollActivateOfUCSM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollDebundlePort

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollDebundlePort

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:PollUpdateOfIOM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for update of IOMs to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollUpdateOfIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-ofiom-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployPollUpdateOfIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ResolveDistributable

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployResolveDistributable

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ResolveDistributableNames

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Resolving distributable name from infra pack(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployResolveDistributableNames

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:ResolveImages

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployResolveImages

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:UpdateIOM

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Updating back-up image of IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:UpdateIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateiom-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployUpdateIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:WaitForDeploy

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Deploy to begin(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForDeploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-deploy-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployWaitForDeploy

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemDeploy:WaitForUserAck

Fault Code: F17408

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for User Acknowledgement To Start Primary Fabric Interconnect Activation(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForUserAck)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-user-ack-failed

mibFaultCode: 17408

mibFaultName: fsmStFailFirmwareSystemDeployWaitForUserAck

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemApplyCatalogPack:ActivateCatalog

Fault Code: F17409

Message

[FSM:STAGE:FAILED|RETRY]: Activating Catalog(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ActivateCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-catalog-failed

mibFaultCode: 17409

mibFaultName: fsmStFailFirmwareSystemApplyCatalogPackActivateCatalog

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemApplyCatalogPack:ResolveDistributable

Fault Code: F17409

Message

[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 17409

mibFaultName: fsmStFailFirmwareSystemApplyCatalogPackResolveDistributable

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemApplyCatalogPack:ResolveDistributableNames

Fault Code: F17409

Message

[FSM:STAGE:FAILED|RETRY]: Resolving distributable name(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 17409

mibFaultName: fsmStFailFirmwareSystemApplyCatalogPackResolveDistributableNames

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailFirmwareSystemApplyCatalogPack:ResolveImages

Fault Code: F17409

Message

[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 17409

mibFaultName: fsmStFailFirmwareSystemApplyCatalogPackResolveImages

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmStFailComputeServerDiscPolicyResolveScrubPolicy:Resolve

Fault Code: F17426

Message

[FSM:STAGE:FAILED|RETRY]: Resolving scrub policy from Firepower Central(FSM-STAGE:sam:dme:ComputeServerDiscPolicyResolveScrubPolicy:Resolve)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-failed

mibFaultCode: 17426

mibFaultName: fsmStFailComputeServerDiscPolicyResolveScrubPolicyResolve

moClass: compute:ServerDiscPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/server-discovery

fsmStFailSwFcSanBorderActivateZoneSet:UpdateZones

Fault Code: F17439

Message

[FSM:STAGE:FAILED|RETRY]: fc zone configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderActivateZoneSet:UpdateZones)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-zones-failed

mibFaultCode: 17439

mibFaultName: fsmStFailSwFcSanBorderActivateZoneSetUpdateZones

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmStFailExtpolEpRepairCert:cleanOldData

Fault Code: F17446

Message

[FSM:STAGE:FAILED|RETRY]: Cleaning certificates, channels and policy meta data(FSM-STAGE:sam:dme:ExtpolEpRepairCert:cleanOldData)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clean-old-data-failed

mibFaultCode: 17446

mibFaultName: fsmStFailExtpolEpRepairCertCleanOldData

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailExtpolEpRepairCert:request

Fault Code: F17446

Message

[FSM:STAGE:FAILED|RETRY]: Provisioning latest certificates(FSM-STAGE:sam:dme:ExtpolEpRepairCert:request)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-failed

mibFaultCode: 17446

mibFaultName: fsmStFailExtpolEpRepairCertRequest

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailExtpolEpRepairCert:unregister

Fault Code: F17446

Message

[FSM:STAGE:FAILED|RETRY]: unregister from old FPR Central, if needed(FSM-STAGE:sam:dme:ExtpolEpRepairCert:unregister)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unregister-failed

mibFaultCode: 17446

mibFaultName: fsmStFailExtpolEpRepairCertUnregister

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailExtpolEpRepairCert:verify

Fault Code: F17446

Message

[FSM:STAGE:FAILED|RETRY]: checking that cert was provisioned(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 17446

mibFaultName: fsmStFailExtpolEpRepairCertVerify

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailExtpolEpRepairCert:verifyGuid

Fault Code: F17446

Message

[FSM:STAGE:FAILED|RETRY]: verifying GUID of FPR Central(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verifyGuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-guid-failed

mibFaultCode: 17446

mibFaultName: fsmStFailExtpolEpRepairCertVerifyGuid

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmStFailPolicyControlEpOperate:Resolve

Fault Code: F17447

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyControlEpOperate:Resolve)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-failed

mibFaultCode: 17447

mibFaultName: fsmStFailPolicyControlEpOperateResolve

moClass: policy:ControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]

fsmStFailPolicyPolicyScopeReleasePolicyFsm:Release

Fault Code: F17448

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleasePolicyFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 17448

mibFaultName: fsmStFailPolicyPolicyScopeReleasePolicyFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseOperationFsm:Release

Fault Code: F17449

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseOperationFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 17449

mibFaultName: fsmStFailPolicyPolicyScopeReleaseOperationFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseStorageFsm:Release

Fault Code: F17450

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseStorageFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 17450

mibFaultName: fsmStFailPolicyPolicyScopeReleaseStorageFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveManyPolicyFsm:ResolveMany

Fault Code: F17451

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyPolicyFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 17451

mibFaultName: fsmStFailPolicyPolicyScopeResolveManyPolicyFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveManyOperationFsm:ResolveMany

Fault Code: F17452

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyOperationFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 17452

mibFaultName: fsmStFailPolicyPolicyScopeResolveManyOperationFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveManyStorageFsm:ResolveMany

Fault Code: F17453

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyStorageFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 17453

mibFaultName: fsmStFailPolicyPolicyScopeResolveManyStorageFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany

Fault Code: F17454

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 17454

mibFaultName: fsmStFailPolicyPolicyScopeReleaseManyPolicyFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany

Fault Code: F17455

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 17455

mibFaultName: fsmStFailPolicyPolicyScopeReleaseManyOperationFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany

Fault Code: F17456

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 17456

mibFaultName: fsmStFailPolicyPolicyScopeReleaseManyStorageFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveAllPolicyFsm:ResolveAll

Fault Code: F17457

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllPolicyFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 17457

mibFaultName: fsmStFailPolicyPolicyScopeResolveAllPolicyFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveAllOperationFsm:ResolveAll

Fault Code: F17458

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllOperationFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 17458

mibFaultName: fsmStFailPolicyPolicyScopeResolveAllOperationFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeResolveAllStorageFsm:ResolveAll

Fault Code: F17459

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllStorageFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 17459

mibFaultName: fsmStFailPolicyPolicyScopeResolveAllStorageFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll

Fault Code: F17460

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 17460

mibFaultName: fsmStFailPolicyPolicyScopeReleaseAllPolicyFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll

Fault Code: F17461

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 17461

mibFaultName: fsmStFailPolicyPolicyScopeReleaseAllOperationFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailPolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll

Fault Code: F17462

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 17462

mibFaultName: fsmStFailPolicyPolicyScopeReleaseAllStorageFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmStFailMgmtExportPolicyReportConfigCopy:Report

Fault Code: F17484

Message

[FSM:STAGE:FAILED|RETRY]: Report config copy to Ops Mgr(FSM-STAGE:sam:dme:MgmtExportPolicyReportConfigCopy:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 17484

mibFaultName: fsmStFailMgmtExportPolicyReportConfigCopyReport

moClass: mgmt:ExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/cfg-exp-policy-[name]

Affected MO: org-[name]/db-backup-policy-[name]

fsmStFailExtpolProviderReportConfigImport:Report

Fault Code: F17485

Message

[FSM:STAGE:FAILED|RETRY]: Report config import to Ops Mgr(FSM-STAGE:sam:dme:ExtpolProviderReportConfigImport:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 17485

mibFaultName: fsmStFailExtpolProviderReportConfigImportReport

moClass: extpol:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]

fsmStFailObserveObservedResolvePolicyFsm:Execute

Fault Code: F17491

Message

[FSM:STAGE:FAILED|RETRY]: Resolve Policy FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolvePolicyFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17491

mibFaultName: fsmStFailObserveObservedResolvePolicyFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmStFailObserveObservedResolveResourceFsm:Execute

Fault Code: F17492

Message

[FSM:STAGE:FAILED|RETRY]: Resolve Resource FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveResourceFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17492

mibFaultName: fsmStFailObserveObservedResolveResourceFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmStFailObserveObservedResolveVMFsm:Execute

Fault Code: F17493

Message

[FSM:STAGE:FAILED|RETRY]: Resolve VM FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveVMFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17493

mibFaultName: fsmStFailObserveObservedResolveVMFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmStFailObserveObservedResolveControllerFsm:Execute

Fault Code: F17494

Message

[FSM:STAGE:FAILED|RETRY]: Resolve Mgmt Controller FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveControllerFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17494

mibFaultName: fsmStFailObserveObservedResolveControllerFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmStFailMgmtControllerRegistryConfig:Remove

Fault Code: F17499

Message

[FSM:STAGE:FAILED|RETRY]: Deleting registry information from config file(FSM-STAGE:sam:dme:MgmtControllerRegistryConfig:Remove)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-failed

mibFaultCode: 17499

mibFaultName: fsmStFailMgmtControllerRegistryConfigRemove

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailGmetaHolderInventory:CheckInventoryStatus

Fault Code: F17608

Message

[FSM:STAGE:FAILED|RETRY]: Throttle inventory(FSM-STAGE:sam:dme:GmetaHolderInventory:CheckInventoryStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-inventory-status-failed

mibFaultCode: 17608

mibFaultName: fsmStFailGmetaHolderInventoryCheckInventoryStatus

moClass: gmeta:Holder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: gmeta/category-[category]-provider-[provider]

fsmStFailGmetaHolderInventory:ReportFullInventory

Fault Code: F17608

Message

[FSM:STAGE:FAILED|RETRY]: Report inventory to Firepower Central(FSM-STAGE:sam:dme:GmetaHolderInventory:ReportFullInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-full-inventory-failed

mibFaultCode: 17608

mibFaultName: fsmStFailGmetaHolderInventoryReportFullInventory

moClass: gmeta:Holder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: gmeta/category-[category]-provider-[provider]

fsmStFailComputePhysicalCimcSessionDelete:Execute

Fault Code: F17609

Message

[FSM:STAGE:FAILED|RETRY]: Terminating Cimc Sessions(FSM-STAGE:sam:dme:ComputePhysicalCimcSessionDelete:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17609

mibFaultName: fsmStFailComputePhysicalCimcSessionDeleteExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailPolicyControlledTypeOperate:ResolveAll

Fault Code: F17612

Message

[FSM:STAGE:FAILED|RETRY]: Resolving controlled type global policies(FSM-STAGE:sam:dme:PolicyControlledTypeOperate:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 17612

mibFaultName: fsmStFailPolicyControlledTypeOperateResolveAll

moClass: policy:ControlledType

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]/cfg-backup-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/comm-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/datetime-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/discovery-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/dns-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fabric-fw-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fault-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/mep-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/monitoring-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/powermgmt-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/psu-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/security-ctrl/ctrlled-type-[type]

fsmStFailFabricVnetEpSyncEpPushVnetEpDeletion:Sync

Fault Code: F17619

Message

[FSM:STAGE:FAILED|RETRY]: Update resource-mgr with VnetEp deletion(FSM-STAGE:sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion:Sync)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-failed

mibFaultCode: 17619

mibFaultName: fsmStFailFabricVnetEpSyncEpPushVnetEpDeletionSync

moClass: fabric:VnetEpSyncEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]/syncEp

fsmStFailSwEthLanFlowMonDeploy:UpdateEthFlowMon

Fault Code: F17639

Message

[FSM:STAGE:FAILED|RETRY]: Ethernet traffic flow monitoring configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanFlowMonDeploy:UpdateEthFlowMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-eth-flow-mon-failed

mibFaultCode: 17639

mibFaultName: fsmStFailSwEthLanFlowMonDeployUpdateEthFlowMon

moClass: sw:EthLanFlowMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ethlanflowmon

fsmStFailMgmtIPv6IfAddrSwMgmtOobIpv6IfConfig:Switch

Fault Code: F17665

Message

[FSM:STAGE:FAILED|RETRY]: configuring the out-of-band IPv6 interface(FSM-STAGE:sam:dme:MgmtIPv6IfAddrSwMgmtOobIpv6IfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 17665

mibFaultName: fsmStFailMgmtIPv6IfAddrSwMgmtOobIpv6IfConfigSwitch

moClass: mgmt:IPv6IfAddr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

fsmStFailComputePhysicalUpdateBoardController:PollUpdateStatus

Fault Code: F17667

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 17667

mibFaultName: fsmStFailComputePhysicalUpdateBoardControllerPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBoardController:PrepareForUpdate

Fault Code: F17667

Message

[FSM:STAGE:FAILED|RETRY]: Prepare for BoardController update(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:PrepareForUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-for-update-failed

mibFaultCode: 17667

mibFaultName: fsmStFailComputePhysicalUpdateBoardControllerPrepareForUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBoardController:ServerPowerOff

Fault Code: F17667

Message

[FSM:STAGE:FAILED|RETRY]: Power off server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:ServerPowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: server-power-off-failed

mibFaultCode: 17667

mibFaultName: fsmStFailComputePhysicalUpdateBoardControllerServerPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBoardController:ServerPowerOn

Fault Code: F17667

Message

[FSM:STAGE:FAILED|RETRY]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:ServerPowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: server-power-on-failed

mibFaultCode: 17667

mibFaultName: fsmStFailComputePhysicalUpdateBoardControllerServerPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalUpdateBoardController:UpdateRequest

Fault Code: F17667

Message

[FSM:STAGE:FAILED|RETRY]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 17667

mibFaultName: fsmStFailComputePhysicalUpdateBoardControllerUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailExtvmmNetworkSetsDeploy:Local

Fault Code: F17703

Message

[FSM:STAGE:FAILED|RETRY]: VMNetworkDefinition configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmNetworkSetsDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17703

mibFaultName: fsmStFailExtvmmNetworkSetsDeployLocal

moClass: extvmm:NetworkSets

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets

fsmStFailExtvmmNetworkSetsDeploy:Peer

Fault Code: F17703

Message

[FSM:STAGE:FAILED|RETRY]: VMNetworkDefinition configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmNetworkSetsDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 17703

mibFaultName: fsmStFailExtvmmNetworkSetsDeployPeer

moClass: extvmm:NetworkSets

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets

fsmStFailComputePhysicalConfigBoard:ConfigMemoryPolicy

Fault Code: F17707

Message

[FSM:STAGE:FAILED|RETRY]: Configure Memory Configuration Policy on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigBoard:ConfigMemoryPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-memory-policy-failed

mibFaultCode: 17707

mibFaultName: fsmStFailComputePhysicalConfigBoardConfigMemoryPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalResetMemoryErrors:Execute

Fault Code: F17708

Message

[FSM:STAGE:FAILED|RETRY]: Resetting memory errors on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetMemoryErrors:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17708

mibFaultName: fsmStFailComputePhysicalResetMemoryErrorsExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailMgmtControllerExtMgmtInterfaceConfig:Active

Fault Code: F17714

Message

[FSM:STAGE:FAILED|RETRY]: external in-band mgmt interface configuration on Active CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:Active)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: active-failed

mibFaultCode: 17714

mibFaultName: fsmStFailMgmtControllerExtMgmtInterfaceConfigActive

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgLocal

Fault Code: F17714

Message

[FSM:STAGE:FAILED|RETRY]: in-band vlan configuration on Local CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cimcvlan-cfg-local-failed

mibFaultCode: 17714

mibFaultName: fsmStFailMgmtControllerExtMgmtInterfaceConfigCIMCVlanCfgLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgPeer

Fault Code: F17714

Message

[FSM:STAGE:FAILED|RETRY]: in-band vlan configuration on Peer CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cimcvlan-cfg-peer-failed

mibFaultCode: 17714

mibFaultName: fsmStFailMgmtControllerExtMgmtInterfaceConfigCIMCVlanCfgPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerExtMgmtInterfaceConfig:CMCVlanCfg

Fault Code: F17714

Message

[FSM:STAGE:FAILED|RETRY]: in-band vlan configuration on CMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CMCVlanCfg)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cmcvlan-cfg-failed

mibFaultCode: 17714

mibFaultName: fsmStFailMgmtControllerExtMgmtInterfaceConfigCMCVlanCfg

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailMgmtControllerExtMgmtInterfaceConfig:CMCVlanCfgPeer

Fault Code: F17714

Message

[FSM:STAGE:FAILED|RETRY]: in-band vlan configuration on CMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CMCVlanCfgPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cmcvlan-cfg-peer-failed

mibFaultCode: 17714

mibFaultName: fsmStFailMgmtControllerExtMgmtInterfaceConfigCMCVlanCfgPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailComputeRackUnitCreateDhcpEntry:ExecuteLocal

Fault Code: F17715

Message

[FSM:STAGE:FAILED|RETRY]: Creating host entry in dhcp database(FSM-STAGE:sam:dme:ComputeRackUnitCreateDhcpEntry:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 17715

mibFaultName: fsmStFailComputeRackUnitCreateDhcpEntryExecuteLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputeRackUnitCreateDhcpEntry:ExecutePeer

Fault Code: F17715

Message

[FSM:STAGE:FAILED|RETRY]: Creating host entry in dhcp database(FSM-STAGE:sam:dme:ComputeRackUnitCreateDhcpEntry:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 17715

mibFaultName: fsmStFailComputeRackUnitCreateDhcpEntryExecutePeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraDeploy:NicConfigLocal

Fault Code: F17716

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:NicConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-local-failed

mibFaultCode: 17716

mibFaultName: fsmStFailComputePhysicalServiceInfraDeployNicConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraDeploy:NicConfigPeer

Fault Code: F17716

Message

[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:NicConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-peer-failed

mibFaultCode: 17716

mibFaultName: fsmStFailComputePhysicalServiceInfraDeployNicConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraDeploy:SwConfigLocal

Fault Code: F17716

Message

[FSM:STAGE:FAILED|RETRY]: Configure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 17716

mibFaultName: fsmStFailComputePhysicalServiceInfraDeploySwConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraDeploy:SwConfigPeer

Fault Code: F17716

Message

[FSM:STAGE:FAILED|RETRY]: Configure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 17716

mibFaultName: fsmStFailComputePhysicalServiceInfraDeploySwConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraWithdraw:NicUnConfigLocal

Fault Code: F17717

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:NicUnConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-un-config-local-failed

mibFaultCode: 17717

mibFaultName: fsmStFailComputePhysicalServiceInfraWithdrawNicUnConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraWithdraw:NicUnConfigPeer

Fault Code: F17717

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:NicUnConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-un-config-peer-failed

mibFaultCode: 17717

mibFaultName: fsmStFailComputePhysicalServiceInfraWithdrawNicUnConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraWithdraw:SwUnConfigLocal

Fault Code: F17717

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:SwUnConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-un-config-local-failed

mibFaultCode: 17717

mibFaultName: fsmStFailComputePhysicalServiceInfraWithdrawSwUnConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalServiceInfraWithdraw:SwUnConfigPeer

Fault Code: F17717

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:SwUnConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-un-config-peer-failed

mibFaultCode: 17717

mibFaultName: fsmStFailComputePhysicalServiceInfraWithdrawSwUnConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailEquipmentIOCardBaseFePresence:CheckLicense

Fault Code: F17808

Message

[FSM:STAGE:FAILED|RETRY]: Checking license for chassis [chassisId] (iom [id])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:CheckLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-license-failed

mibFaultCode: 17808

mibFaultName: fsmStFailEquipmentIOCardBaseFePresenceCheckLicense

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFePresence:ConfigChassisId

Fault Code: F17808

Message

[FSM:STAGE:FAILED|RETRY]: identifying SwitchIOCard [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:ConfigChassisId)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-chassis-id-failed

mibFaultCode: 17808

mibFaultName: fsmStFailEquipmentIOCardBaseFePresenceConfigChassisId

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFePresence:Identify

Fault Code: F17808

Message

[FSM:STAGE:FAILED|RETRY]: identifying IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:Identify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: identify-failed

mibFaultCode: 17808

mibFaultName: fsmStFailEquipmentIOCardBaseFePresenceIdentify

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:ConfigureEndPoint

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: configuring management identity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-end-point-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnConfigureEndPoint

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:ConfigureSwMgmtEndPoint

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: configuring fabric interconnect [switchId] mgmt connectivity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureSwMgmtEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-sw-mgmt-end-point-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnConfigureSwMgmtEndPoint

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:ConfigureVifNs

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: configuring IOM [chassisId]/[id]([side]) virtual name space(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureVifNs)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-vif-ns-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnConfigureVifNs

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:DiscoverChassis

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: triggerring chassis discovery via IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:DiscoverChassis)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: discover-chassis-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnDiscoverChassis

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:EnableChassis

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: enabling chassis [chassisId] on [side] side(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:EnableChassis)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-chassis-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnEnableChassis

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailEquipmentIOCardBaseFeConn:ResetBlades

Fault Code: F17809

Message

[FSM:STAGE:FAILED|RETRY]: Reset Security Modules on [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ResetBlades)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-blades-failed

mibFaultCode: 17809

mibFaultName: fsmStFailEquipmentIOCardBaseFeConnResetBlades

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmStFailMgmtControllerLockConfig:PowerButtonLockConfig

Fault Code: F17813

Message

[FSM:STAGE:FAILED|RETRY]: Configuring Power Button Lock State(FSM-STAGE:sam:dme:MgmtControllerLockConfig:PowerButtonLockConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-button-lock-config-failed

mibFaultCode: 17813

mibFaultName: fsmStFailMgmtControllerLockConfigPowerButtonLockConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmStFailSdAppInstanceInstallApplication:Install

Fault Code: F17819

Message

[FSM:STAGE:FAILED|RETRY]: Installing application(FSM-STAGE:sam:dme:SdAppInstanceInstallApplication:Install)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: install-failed

mibFaultCode: 17819

mibFaultName: fsmStFailSdAppInstanceInstallApplicationInstall

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceInstallApplication:UpdateAppInstance

Fault Code: F17819

Message

[FSM:STAGE:FAILED|RETRY]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceInstallApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 17819

mibFaultName: fsmStFailSdAppInstanceInstallApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSysdebugLogExportPolicyConfigure:Local

Fault Code: F17830

Message

[FSM:STAGE:FAILED|RETRY]: configuring log file export service on local(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Local)

Explanation

Cisco Firepower Manager could not set the configurations in the primary Fabric Interconnect for log file transfer to remote server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17830

mibFaultName: fsmStFailSysdebugLogExportPolicyConfigureLocal

moClass: sysdebug:LogExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy

fsmStFailSysdebugLogExportPolicyConfigure:Peer

Fault Code: F17830

Message

[FSM:STAGE:FAILED|RETRY]: configuring log file export service on peer(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Peer)

Explanation

Cisco Firepower Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for log file transfer to remote server. This fault typically appears for one of the following reasons:

- The subordinate FI is not reachable.

- The subordinate FI is experiencing an internal system error on applying the configuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FI cluster state to ensure that the subordinate FI is reachable and functioning correctly. If the subordinate FI is down, take appropriate corrective actions so that the Firepower cluster goes into HA ready state.

Step 2 If the HA state of the primary and subordinate FIs are good, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 17830

mibFaultName: fsmStFailSysdebugLogExportPolicyConfigurePeer

moClass: sysdebug:LogExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy

fsmStFailComputePhysicalFlashController:UpdateFlashLife

Fault Code: F17839

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Flash Life update to complete(FSM-STAGE:sam:dme:ComputePhysicalFlashController:UpdateFlashLife)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-flash-life-failed

mibFaultCode: 17839

mibFaultName: fsmStFailComputePhysicalFlashControllerUpdateFlashLife

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailOsControllerDeployOS:HostCheckImageValidationStatus

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Check for image validation status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckImageValidationStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-image-validation-status-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostCheckImageValidationStatus

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostCheckRommonReady

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Check for the Rommon first response status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckRommonReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-rommon-ready-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostCheckRommonReady

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostCheckUpgradeImageStatus

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Check for the image tftp status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckUpgradeImageStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-upgrade-image-status-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostCheckUpgradeImageStatus

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostPrepareBoot

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Prepare the boot command for [chassisId]/[slotId] and then boot the blade(FSM-STAGE:sam:dme:OsControllerDeployOS:HostPrepareBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-boot-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostPrepareBoot

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostPrepareKeyFile

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:OsControllerDeployOS:HostPrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-key-file-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostPrepareKeyFile

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostWaitForRommonReady

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Wait for Rommon on blade [chassisId]/[slotId] to update the bootstatus.txt file(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForRommonReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-rommon-ready-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostWaitForRommonReady

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostWaitForRommonValidateImage

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Wait for Rommon on blade [chassisId]/[slotId] to update the bootstatus.txt file(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForRommonValidateImage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-rommon-validate-image-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostWaitForRommonValidateImage

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerDeployOS:HostWaitForSspOsRunning

Fault Code: F17863

Message

[FSM:STAGE:FAILED|RETRY]: Wait for OS on blade [chassisId]/[slotId] in service(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForSspOsRunning)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-ssp-os-running-failed

mibFaultCode: 17863

mibFaultName: fsmStFailOsControllerDeployOSHostWaitForSspOsRunning

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailNhTableHolderConfigureLinks:ApplyConfig

Fault Code: F17866

Message

[FSM:STAGE:FAILED|RETRY]: Apply Configuration(FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 17866

mibFaultName: fsmStFailNhTableHolderConfigureLinksApplyConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmStFailNhTableHolderConfigureLinks:ConfigInterface

Fault Code: F17866

Message

[FSM:STAGE:FAILED|RETRY]: Configure Interface(FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:ConfigInterface)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-interface-failed

mibFaultCode: 17866

mibFaultName: fsmStFailNhTableHolderConfigureLinksConfigInterface

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmStFailNhTableHolderConfigureLinks:VerifyLinkConfig

Fault Code: F17866

Message

[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:VerifyLinkConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-link-config-failed

mibFaultCode: 17866

mibFaultName: fsmStFailNhTableHolderConfigureLinksVerifyLinkConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmStFailStorageFlexFlashControllerMOpsReset:Reset

Fault Code: F17872

Message

[FSM:STAGE:FAILED|RETRY]: Resetting FlexFlashController [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsReset:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 17872

mibFaultName: fsmStFailStorageFlexFlashControllerMOpsResetReset

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmStFailStorageFlexFlashControllerMOpsFormat:Format

Fault Code: F17873

Message

[FSM:STAGE:FAILED|RETRY]: Formatting FlexFlash Cards in Controller [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsFormat:Format)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: format-failed

mibFaultCode: 17873

mibFaultName: fsmStFailStorageFlexFlashControllerMOpsFormatFormat

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmStFailStorageFlexFlashControllerMOpsPair:Pair

Fault Code: F17874

Message

[FSM:STAGE:FAILED|RETRY]: Pair FlexFlash Cards in Controller [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsPair:Pair)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pair-failed

mibFaultCode: 17874

mibFaultName: fsmStFailStorageFlexFlashControllerMOpsPairPair

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmStFailIdentMetaSystemUcscUnivSync:Execute

Fault Code: F17877

Message

[FSM:STAGE:FAILED|RETRY]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemUcscUnivSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 17877

mibFaultName: fsmStFailIdentMetaSystemUcscUnivSyncExecute

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmStFailComputePhysicalEnableCimcSecureBoot:Activate

Fault Code: F17897

Message

[FSM:STAGE:FAILED|RETRY]: Activating CIMC image(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 17897

mibFaultName: fsmStFailComputePhysicalEnableCimcSecureBootActivate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalEnableCimcSecureBoot:PollUpdateStatus

Fault Code: F17897

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 17897

mibFaultName: fsmStFailComputePhysicalEnableCimcSecureBootPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalEnableCimcSecureBoot:Reset

Fault Code: F17897

Message

[FSM:STAGE:FAILED|RETRY]: Resetting CIMC to boot the activated version(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 17897

mibFaultName: fsmStFailComputePhysicalEnableCimcSecureBootReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailComputePhysicalEnableCimcSecureBoot:UpdateRequest

Fault Code: F17897

Message

[FSM:STAGE:FAILED|RETRY]: Sending update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 17897

mibFaultName: fsmStFailComputePhysicalEnableCimcSecureBootUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmStFailSdAppInstanceStartApplication:DebundlePorts

Fault Code: F17911

Message

[FSM:STAGE:FAILED|RETRY]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 17911

mibFaultName: fsmStFailSdAppInstanceStartApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStartApplication:Start

Fault Code: F17911

Message

[FSM:STAGE:FAILED|RETRY]: Starting application(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:Start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 17911

mibFaultName: fsmStFailSdAppInstanceStartApplicationStart

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStartApplication:UpdateAppInstance

Fault Code: F17911

Message

[FSM:STAGE:FAILED|RETRY]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 17911

mibFaultName: fsmStFailSdAppInstanceStartApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdLduProvisionLDU:CheckBladeReadiness

Fault Code: F17912

Message

[FSM:STAGE:FAILED|RETRY]: Check if the blade is available to provision logical device.(FSM-STAGE:sam:dme:SdLduProvisionLDU:CheckBladeReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-blade-readiness-failed

mibFaultCode: 17912

mibFaultName: fsmStFailSdLduProvisionLDUCheckBladeReadiness

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmStFailSdLduProvisionLDU:StartApps

Fault Code: F17912

Message

[FSM:STAGE:FAILED|RETRY]: Start the Apps(FSM-STAGE:sam:dme:SdLduProvisionLDU:StartApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-apps-failed

mibFaultCode: 17912

mibFaultName: fsmStFailSdLduProvisionLDUStartApps

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmStFailSdLduProvisionLDU:WaitForAppsInstallation

Fault Code: F17912

Message

[FSM:STAGE:FAILED|RETRY]: Wait for all the apps in the LDU to get installed.(FSM-STAGE:sam:dme:SdLduProvisionLDU:WaitForAppsInstallation)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-apps-installation-failed

mibFaultCode: 17912

mibFaultName: fsmStFailSdLduProvisionLDUWaitForAppsInstallation

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmStFailSdLduProvisionLDU:WaitForLinkConfiguration

Fault Code: F17912

Message

[FSM:STAGE:FAILED|RETRY]: Wait for CCL and MGMT Links configuration(FSM-STAGE:sam:dme:SdLduProvisionLDU:WaitForLinkConfiguration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-link-configuration-failed

mibFaultCode: 17912

mibFaultName: fsmStFailSdLduProvisionLDUWaitForLinkConfiguration

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmStFailSwExtUtilityConfPortBreakout:ConfigSwA

Fault Code: F17917

Message

[FSM:STAGE:FAILED|RETRY]: Configure port breakout mode mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:ConfigSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-afailed

mibFaultCode: 17917

mibFaultName: fsmStFailSwExtUtilityConfPortBreakoutConfigSwA

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmStFailSwExtUtilityConfPortBreakout:ConfigSwB

Fault Code: F17917

Message

[FSM:STAGE:FAILED|RETRY]: Configure port breakout mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:ConfigSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-bfailed

mibFaultCode: 17917

mibFaultName: fsmStFailSwExtUtilityConfPortBreakoutConfigSwB

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmStFailSwExtUtilityConfPortBreakout:PortInventorySwA

Fault Code: F17917

Message

[FSM:STAGE:FAILED|RETRY]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:PortInventorySwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-afailed

mibFaultCode: 17917

mibFaultName: fsmStFailSwExtUtilityConfPortBreakoutPortInventorySwA

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmStFailSwExtUtilityConfPortBreakout:PortInventorySwB

Fault Code: F17917

Message

[FSM:STAGE:FAILED|RETRY]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:PortInventorySwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-bfailed

mibFaultCode: 17917

mibFaultName: fsmStFailSwExtUtilityConfPortBreakoutPortInventorySwB

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmStFailSwExtUtilityConfPortBreakout:VerifyBreakoutConfig

Fault Code: F17917

Message

[FSM:STAGE:FAILED|RETRY]: Verifying physical port breakout config on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:VerifyBreakoutConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-breakout-config-failed

mibFaultCode: 17917

mibFaultName: fsmStFailSwExtUtilityConfPortBreakoutVerifyBreakoutConfig

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmStFailNhTableHolderBootstrapLinks:ApplyConfig

Fault Code: F17920

Message

[FSM:STAGE:FAILED|RETRY]: Apply Configuration(FSM-STAGE:sam:dme:NhTableHolderBootstrapLinks:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 17920

mibFaultName: fsmStFailNhTableHolderBootstrapLinksApplyConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmStFailLicenseSmartConfigSetConfig:Local

Fault Code: F17922

Message

[FSM:STAGE:FAILED|RETRY]: Smart config change(FSM-STAGE:sam:dme:LicenseSmartConfigSetConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17922

mibFaultName: fsmStFailLicenseSmartConfigSetConfigLocal

moClass: license:SmartConfig

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/license-config-[operation]

fsmStFailApplicationDownloaderDownload:Local

Fault Code: F17928

Message

[FSM:STAGE:FAILED|RETRY]: downloading image [fileName] from [server](FSM-STAGE:sam:dme:ApplicationDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17928

mibFaultName: fsmStFailApplicationDownloaderDownloadLocal

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmStFailApplicationDownloaderDownload:UnpackLocal

Fault Code: F17928

Message

[FSM:STAGE:FAILED|RETRY]: unpacking image [fileName] on primary(FSM-STAGE:sam:dme:ApplicationDownloaderDownload:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 17928

mibFaultName: fsmStFailApplicationDownloaderDownloadUnpackLocal

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmStFailApplicationDownloaderDownload:Verify

Fault Code: F17928

Message

[FSM:STAGE:FAILED|RETRY]: Image validation in progress(FSM-STAGE:sam:dme:ApplicationDownloaderDownload:Verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 17928

mibFaultName: fsmStFailApplicationDownloaderDownloadVerify

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmStFailSmAppDelete:Local

Fault Code: F17948

Message

[FSM:STAGE:FAILED|RETRY]: deleting the Application [name].[version](FSM-STAGE:sam:dme:SmAppDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 17948

mibFaultName: fsmStFailSmAppDeleteLocal

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmStFailSmSecSvcRestoreApplication:Restore

Fault Code: F17949

Message

[FSM:STAGE:FAILED|RETRY]: Restoring Apps in progress(FSM-STAGE:sam:dme:SmSecSvcRestoreApplication:Restore)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-failed

mibFaultCode: 17949

mibFaultName: fsmStFailSmSecSvcRestoreApplicationRestore

moClass: sm:SecSvc

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc

fsmStFailOsControllerUpgradeOS:HostWaitForUpgradeComplete

Fault Code: F17964

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for upgrade complete from blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:HostWaitForUpgradeComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-upgrade-complete-failed

mibFaultCode: 17964

mibFaultName: fsmStFailOsControllerUpgradeOSHostWaitForUpgradeComplete

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerUpgradeOS:RebootHostAfterUpgrade

Fault Code: F17964

Message

[FSM:STAGE:FAILED|RETRY]: Reboot blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:RebootHostAfterUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reboot-host-after-upgrade-failed

mibFaultCode: 17964

mibFaultName: fsmStFailOsControllerUpgradeOSRebootHostAfterUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerUpgradeOS:RequestToUpgrade

Fault Code: F17964

Message

[FSM:STAGE:FAILED|RETRY]: Request for upgrade to blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:RequestToUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-to-upgrade-failed

mibFaultCode: 17964

mibFaultName: fsmStFailOsControllerUpgradeOSRequestToUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerInitOS:HostPrepareBoot

Fault Code: F17965

Message

[FSM:STAGE:FAILED|RETRY]: Prepare the boot command for blade [chassisId]/[slotId] to keep it in sync with MO(FSM-STAGE:sam:dme:OsControllerInitOS:HostPrepareBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-boot-failed

mibFaultCode: 17965

mibFaultName: fsmStFailOsControllerInitOSHostPrepareBoot

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerInitOS:HostWaitForUpgradeComplete

Fault Code: F17965

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for upgrade complete from blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:HostWaitForUpgradeComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-upgrade-complete-failed

mibFaultCode: 17965

mibFaultName: fsmStFailOsControllerInitOSHostWaitForUpgradeComplete

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerInitOS:RebootHostAfterUpgrade

Fault Code: F17965

Message

[FSM:STAGE:FAILED|RETRY]: Reboot blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:RebootHostAfterUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reboot-host-after-upgrade-failed

mibFaultCode: 17965

mibFaultName: fsmStFailOsControllerInitOSRebootHostAfterUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailOsControllerInitOS:RequestToUpgrade

Fault Code: F17965

Message

[FSM:STAGE:FAILED|RETRY]: Request for upgrade to blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:RequestToUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-to-upgrade-failed

mibFaultCode: 17965

mibFaultName: fsmStFailOsControllerInitOSRequestToUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmStFailSdAppInstanceUpgradeApplication:DebundlePorts

Fault Code: F17966

Message

[FSM:STAGE:FAILED|RETRY]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 17966

mibFaultName: fsmStFailSdAppInstanceUpgradeApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceUpgradeApplication:UpdateAppInstance

Fault Code: F17966

Message

[FSM:STAGE:FAILED|RETRY]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 17966

mibFaultName: fsmStFailSdAppInstanceUpgradeApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceUpgradeApplication:Upgrade

Fault Code: F17966

Message

[FSM:STAGE:FAILED|RETRY]: Upgrading application(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:Upgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upgrade-failed

mibFaultCode: 17966

mibFaultName: fsmStFailSdAppInstanceUpgradeApplicationUpgrade

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStopApplication:DebundlePorts

Fault Code: F17967

Message

[FSM:STAGE:FAILED|RETRY]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 17967

mibFaultName: fsmStFailSdAppInstanceStopApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStopApplication:ReleaseAppLicense

Fault Code: F17967

Message

[FSM:STAGE:FAILED|RETRY]: Release license of application instance(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:ReleaseAppLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-app-license-failed

mibFaultCode: 17967

mibFaultName: fsmStFailSdAppInstanceStopApplicationReleaseAppLicense

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStopApplication:Stop

Fault Code: F17967

Message

[FSM:STAGE:FAILED|RETRY]: Stopping application(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:Stop)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-failed

mibFaultCode: 17967

mibFaultName: fsmStFailSdAppInstanceStopApplicationStop

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceStopApplication:UpdateAppInstance

Fault Code: F17967

Message

[FSM:STAGE:FAILED|RETRY]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 17967

mibFaultName: fsmStFailSdAppInstanceStopApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceUninstallApplication:ReleaseAppLicense

Fault Code: F17968

Message

[FSM:STAGE:FAILED|RETRY]: Release license of application instance(FSM-STAGE:sam:dme:SdAppInstanceUninstallApplication:ReleaseAppLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-app-license-failed

mibFaultCode: 17968

mibFaultName: fsmStFailSdAppInstanceUninstallApplicationReleaseAppLicense

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdAppInstanceUninstallApplication:Uninstall

Fault Code: F17968

Message

[FSM:STAGE:FAILED|RETRY]: Uninstalling application(FSM-STAGE:sam:dme:SdAppInstanceUninstallApplication:Uninstall)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: uninstall-failed

mibFaultCode: 17968

mibFaultName: fsmStFailSdAppInstanceUninstallApplicationUninstall

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmStFailSdSlotChangePlatformLogLevel:SendCommand

Fault Code: F17969

Message

[FSM:STAGE:FAILED|RETRY]: Send command to change the log level(FSM-STAGE:sam:dme:SdSlotChangePlatformLogLevel:SendCommand)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-command-failed

mibFaultCode: 17969

mibFaultName: fsmStFailSdSlotChangePlatformLogLevelSendCommand

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdLogicalDeviceConfigureLinks:ConfigureSwitch

Fault Code: F17971

Message

[FSM:STAGE:FAILED|RETRY]: Invoke Port API to configure the switch(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:ConfigureSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-switch-failed

mibFaultCode: 17971

mibFaultName: fsmStFailSdLogicalDeviceConfigureLinksConfigureSwitch

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdLogicalDeviceConfigureLinks:SendInterfaces

Fault Code: F17971

Message

[FSM:STAGE:FAILED|RETRY]: Send Updated Interface Mapping(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:SendInterfaces)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-interfaces-failed

mibFaultCode: 17971

mibFaultName: fsmStFailSdLogicalDeviceConfigureLinksSendInterfaces

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdLogicalDeviceConfigureLinks:UnconfigureLinks

Fault Code: F17971

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure Links in the LogicalDevice(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:UnconfigureLinks)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfigure-links-failed

mibFaultCode: 17971

mibFaultName: fsmStFailSdLogicalDeviceConfigureLinksUnconfigureLinks

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdLogicalDeviceConfigureLinks:UnconfigureLogicalDevice

Fault Code: F17971

Message

[FSM:STAGE:FAILED|RETRY]: Unconfigure logical device(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:UnconfigureLogicalDevice)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfigure-logical-device-failed

mibFaultCode: 17971

mibFaultName: fsmStFailSdLogicalDeviceConfigureLinksUnconfigureLogicalDevice

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdLogicalDeviceConfigureLinks:WaitForSwitchConfig

Fault Code: F17971

Message

[FSM:STAGE:FAILED|RETRY]: Wait for Switch configuration to complete(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:WaitForSwitchConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-config-failed

mibFaultCode: 17971

mibFaultName: fsmStFailSdLogicalDeviceConfigureLinksWaitForSwitchConfig

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdSlotFormatDisk:CheckBladeReadiness

Fault Code: F17974

Message

[FSM:STAGE:FAILED|RETRY]: Check blade readiness(FSM-STAGE:sam:dme:SdSlotFormatDisk:CheckBladeReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-blade-readiness-failed

mibFaultCode: 17974

mibFaultName: fsmStFailSdSlotFormatDiskCheckBladeReadiness

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdSlotFormatDisk:ResetBladePower

Fault Code: F17974

Message

[FSM:STAGE:FAILED|RETRY]: Blade power reset(FSM-STAGE:sam:dme:SdSlotFormatDisk:ResetBladePower)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-blade-power-failed

mibFaultCode: 17974

mibFaultName: fsmStFailSdSlotFormatDiskResetBladePower

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdSlotFormatDisk:StartDiskFormat

Fault Code: F17974

Message

[FSM:STAGE:FAILED|RETRY]: Start formatting disk(FSM-STAGE:sam:dme:SdSlotFormatDisk:StartDiskFormat)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-disk-format-failed

mibFaultCode: 17974

mibFaultName: fsmStFailSdSlotFormatDiskStartDiskFormat

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdSlotFormatDisk:WaitForDiskFormatComplete

Fault Code: F17974

Message

[FSM:STAGE:FAILED|RETRY]: Wait for disk format complete(FSM-STAGE:sam:dme:SdSlotFormatDisk:WaitForDiskFormatComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-disk-format-complete-failed

mibFaultCode: 17974

mibFaultName: fsmStFailSdSlotFormatDiskWaitForDiskFormatComplete

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdSlotSynchTimeZone:UpdateTimeZone

Fault Code: F17975

Message

[FSM:STAGE:FAILED|RETRY]: Update time zone(FSM-STAGE:sam:dme:SdSlotSynchTimeZone:UpdateTimeZone)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-time-zone-failed

mibFaultCode: 17975

mibFaultName: fsmStFailSdSlotSynchTimeZoneUpdateTimeZone

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmStFailSdAppAttributeCtrlGetAppAttributes:GetAttributes

Fault Code: F17976

Message

[FSM:STAGE:FAILED|RETRY]: Retrive application attributes(FSM-STAGE:sam:dme:SdAppAttributeCtrlGetAppAttributes:GetAttributes)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: get-attributes-failed

mibFaultCode: 17976

mibFaultName: fsmStFailSdAppAttributeCtrlGetAppAttributesGetAttributes

moClass: sd:AppAttributeCtrl

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-attribute-ctrl

fsmStFailSdMgmtInfoUpdateMgmtInfo:SendUpdate

Fault Code: F17977

Message

[FSM:STAGE:FAILED|RETRY]: Update management information(FSM-STAGE:sam:dme:SdMgmtInfoUpdateMgmtInfo:SendUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-update-failed

mibFaultCode: 17977

mibFaultName: fsmStFailSdMgmtInfoUpdateMgmtInfoSendUpdate

moClass: sd:MgmtInfo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/mgmt-info

fsmStFailSdNetMgmtBootstrapUpdateNetMgmtBootstrap:SendUpdate

Fault Code: F17978

Message

[FSM:STAGE:FAILED|RETRY]: Send message to AppAgent(FSM-STAGE:sam:dme:SdNetMgmtBootstrapUpdateNetMgmtBootstrap:SendUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-update-failed

mibFaultCode: 17978

mibFaultName: fsmStFailSdNetMgmtBootstrapUpdateNetMgmtBootstrapSendUpdate

moClass: sd:NetMgmtBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/net-mgmt-bootstrap

fsmStFailFirmwarePlatformPackPlatformVersion:Restore

Fault Code: F17984

Message

[FSM:STAGE:FAILED|RETRY]: Check and Restore the Platform Version(FSM-STAGE:sam:dme:FirmwarePlatformPackPlatformVersion:Restore)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-failed

mibFaultCode: 17984

mibFaultName: fsmStFailFirmwarePlatformPackPlatformVersionRestore

moClass: firmware:PlatformPack

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fsmStFailFirmwarePlatformPackPlatformVersion:WaitForReady

Fault Code: F17984

Message

[FSM:STAGE:FAILED|RETRY]: Wait for system to be ready(FSM-STAGE:sam:dme:FirmwarePlatformPackPlatformVersion:WaitForReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-ready-failed

mibFaultCode: 17984

mibFaultName: fsmStFailFirmwarePlatformPackPlatformVersionWaitForReady

moClass: firmware:PlatformPack

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fsmStFailSwSspEthMonDeploy:UpdateSspEthMon

Fault Code: F18000

Message

[FSM:STAGE:FAILED|RETRY]: SSP Packet Capture configuration on [switchId](FSM-STAGE:sam:dme:SwSspEthMonDeploy:UpdateSspEthMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-ssp-eth-mon-failed

mibFaultCode: 18000

mibFaultName: fsmStFailSwSspEthMonDeployUpdateSspEthMon

moClass: sw:SspEthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]

fsmStFailSdClusterBootstrapUpdateClusterConfiguration:SendConfig

Fault Code: F18003

Message

[FSM:STAGE:FAILED|RETRY]: Send Updated Cluster Configuration(FSM-STAGE:sam:dme:SdClusterBootstrapUpdateClusterConfiguration:SendConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-config-failed

mibFaultCode: 18003

mibFaultName: fsmStFailSdClusterBootstrapUpdateClusterConfigurationSendConfig

moClass: sd:ClusterBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/cluster-bootstrap

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/cluster-bootstrap

fsmStFailSmAppUpdateApplication:Update

Fault Code: F18006

Message

[FSM:STAGE:FAILED|RETRY]: Updating Apps in progress(FSM-STAGE:sam:dme:SmAppUpdateApplication:Update)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-failed

mibFaultCode: 18006

mibFaultName: fsmStFailSmAppUpdateApplicationUpdate

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmStFailSmAppInstanceResetApplication:CheckMainAppInstClusterStatus

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Check main app instance cluster status.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:CheckMainAppInstClusterStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-main-app-inst-cluster-status-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationCheckMainAppInstClusterStatus

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:StartApps

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Start main and decorator applications(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StartApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-apps-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationStartApps

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:StopDecoratorApps

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Stop decorator applications(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StopDecoratorApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-decorator-apps-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationStopDecoratorApps

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:StopMainApp

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Stop main application(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StopMainApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-main-app-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationStopMainApp

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:WairForStopDecorators

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Wait for stopping decorator applications to complete(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WairForStopDecorators)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wair-for-stop-decorators-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationWairForStopDecorators

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:WaitForBladeReboot

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Wait for blade reboot(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForBladeReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-reboot-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationWaitForBladeReboot

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:WaitForMainAppInstInCluster

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Wait for main app instance joins cluster.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForMainAppInstInCluster)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-main-app-inst-in-cluster-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationWaitForMainAppInstInCluster

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailSmAppInstanceResetApplication:WaitForStopMainApp

Fault Code: F18007

Message

[FSM:STAGE:FAILED|RETRY]: Wait for stopping main application to complete.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForStopMainApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-stop-main-app-failed

mibFaultCode: 18007

mibFaultName: fsmStFailSmAppInstanceResetApplicationWaitForStopMainApp

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmStFailIpsecEpUpdateEp:ApplyConfig

Fault Code: F18020

Message

[FSM:STAGE:FAILED|RETRY]: configure IPsec connections(FSM-STAGE:sam:dme:IpsecEpUpdateEp:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 18020

mibFaultName: fsmStFailIpsecEpUpdateEpApplyConfig

moClass: ipsec:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext

fsmStFailEtherFtwPortPairConfigFtw:Configure

Fault Code: F18023

Message

[FSM:STAGE:FAILED|RETRY]: Configure fail-to-wire for [dn](FSM-STAGE:sam:dme:EtherFtwPortPairConfigFtw:Configure)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-failed

mibFaultCode: 18023

mibFaultName: fsmStFailEtherFtwPortPairConfigFtwConfigure

moClass: ether:FtwPortPair

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/fail-to-wire/ftw-port-[slotId]-[aggrPortId]-[portId]-port-[peerSlotId]-[peerAggrPortId]-[peerPortId]

fsmStFailSdLinkUpdateInterfaceStatus:SendStatus

Fault Code: F18024

Message

[FSM:STAGE:FAILED|RETRY]: Send Interface Operational State(FSM-STAGE:sam:dme:SdLinkUpdateInterfaceStatus:SendStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-status-failed

mibFaultCode: 18024

mibFaultName: fsmStFailSdLinkUpdateInterfaceStatusSendStatus

moClass: sd:Link

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

fsmStFailSdUpgradeTaskStopUpgradeStartApp:StartApp

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Trigger FSM to start application(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:StartApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-app-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppStartApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSdUpgradeTaskStopUpgradeStartApp:StopApp

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Stop application before upgrade(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:StopApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-app-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppStopApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSdUpgradeTaskStopUpgradeStartApp:UpgradeApp

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Trigger FSM to upgrade application(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:UpgradeApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upgrade-app-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppUpgradeApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSdUpgradeTaskStopUpgradeStartApp:WaitForBladeReboot

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Wait for blade reboot(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForBladeReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-reboot-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppWaitForBladeReboot

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSdUpgradeTaskStopUpgradeStartApp:WaitForStopApp

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Wait for application stop to complete.(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForStopApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-stop-app-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppWaitForStopApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSdUpgradeTaskStopUpgradeStartApp:WaitForUpgradeApp

Fault Code: F18025

Message

[FSM:STAGE:FAILED|RETRY]: Wait for application upgrade to complete.(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForUpgradeApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-upgrade-app-failed

mibFaultCode: 18025

mibFaultName: fsmStFailSdUpgradeTaskStopUpgradeStartAppWaitForUpgradeApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmStFailSwSspEthMonSrcPhyEpDelete:DeletePcapFile

Fault Code: F18034

Message

[FSM:STAGE:FAILED|RETRY]: Delete Pcap file whenever there is a delete interface trigger(FSM-STAGE:sam:dme:SwSspEthMonSrcPhyEpDelete:DeletePcapFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-pcap-file-failed

mibFaultCode: 18034

mibFaultName: fsmStFailSwSspEthMonSrcPhyEpDeleteDeletePcapFile

moClass: sw:SspEthMonSrcPhyEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/ssp-mon-src-phy-[chassisId]-slot-[slotId]-port-[portId]-aggr-[aggrPortId]

fsmStFailFirmwareSupFirmwareDeploy:ActivateFirmwarePack

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Activating SUP Firmware(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:ActivateFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-firmware-pack-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployActivateFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:CheckUpgradeStatus

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Check Upgrade Status(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:CheckUpgradeStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-upgrade-status-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployCheckUpgradeStatus

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:CompleteFirmwareUpgrade

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Complete Firmware Pack Upgrade(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:CompleteFirmwareUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: complete-firmware-upgrade-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployCompleteFirmwareUpgrade

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:DebundlePort

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Debundle the ports(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployDebundlePort

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:PollActivateOfFirmwarePack

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for FPRM Activate to complete(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:PollActivateOfFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-firmware-pack-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployPollActivateOfFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:PollDebundlePort

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployPollDebundlePort

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:UpdateImageVersion

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Updating Image Version(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:UpdateImageVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-image-version-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployUpdateImageVersion

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:UpdatePackageVersion

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Updating Package Version(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:UpdatePackageVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-package-version-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployUpdatePackageVersion

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:ValidateFirmwarePack

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Validate the firmware pack(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:ValidateFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-firmware-pack-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployValidateFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:WaitForDeploy

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Deploy to begin(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:WaitForDeploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-deploy-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployWaitForDeploy

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailFirmwareSupFirmwareDeploy:WaitForFirmwareVersionUpdate

Fault Code: F18035

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Firmware Version to update(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:WaitForFirmwareVersionUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-firmware-version-update-failed

mibFaultCode: 18035

mibFaultName: fsmStFailFirmwareSupFirmwareDeployWaitForFirmwareVersionUpdate

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmStFailEquipmentChassisShutdownChassis:ApplyShutdown

Fault Code: F18043

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown Chassis(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:ApplyShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-shutdown-failed

mibFaultCode: 18043

mibFaultName: fsmStFailEquipmentChassisShutdownChassisApplyShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisShutdownChassis:DebundlePort

Fault Code: F18043

Message

[FSM:STAGE:FAILED|RETRY]: Debundle the ports(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 18043

mibFaultName: fsmStFailEquipmentChassisShutdownChassisDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisShutdownChassis:PollDebundlePort

Fault Code: F18043

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 18043

mibFaultName: fsmStFailEquipmentChassisShutdownChassisPollDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisShutdownChassis:ShutdownBlade

Fault Code: F18043

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown Blade(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:ShutdownBlade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-blade-failed

mibFaultCode: 18043

mibFaultName: fsmStFailEquipmentChassisShutdownChassisShutdownBlade

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisShutdownChassis:WaitForBladeShutdown

Fault Code: F18043

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for blade shutdown(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:WaitForBladeShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-shutdown-failed

mibFaultCode: 18043

mibFaultName: fsmStFailEquipmentChassisShutdownChassisWaitForBladeShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailSmCloudConnectorRegisterCloudConnector:Register

Fault Code: F18051

Message

[FSM:STAGE:FAILED|RETRY]: Registering the device with cloud.(FSM-STAGE:sam:dme:SmCloudConnectorRegisterCloudConnector:Register)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: register-failed

mibFaultCode: 18051

mibFaultName: fsmStFailSmCloudConnectorRegisterCloudConnectorRegister

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmStFailSmCloudConnectorUnRegisterCloudConnector:UnRegister

Fault Code: F18052

Message

[FSM:STAGE:FAILED|RETRY]: UnRegistering the device with cloud.(FSM-STAGE:sam:dme:SmCloudConnectorUnRegisterCloudConnector:UnRegister)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-register-failed

mibFaultCode: 18052

mibFaultName: fsmStFailSmCloudConnectorUnRegisterCloudConnectorUnRegister

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmStFailSmAppVerifyApplication:CheckReadiness

Fault Code: F18053

Message

[FSM:STAGE:FAILED|RETRY]: Image validation queued(FSM-STAGE:sam:dme:SmAppVerifyApplication:CheckReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-readiness-failed

mibFaultCode: 18053

mibFaultName: fsmStFailSmAppVerifyApplicationCheckReadiness

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmStFailSmAppVerifyApplication:Verify

Fault Code: F18053

Message

[FSM:STAGE:FAILED|RETRY]: Image validation in progress(FSM-STAGE:sam:dme:SmAppVerifyApplication:Verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 18053

mibFaultName: fsmStFailSmAppVerifyApplicationVerify

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmStFailSmLogicalDeviceConfigure:ApplyConfig

Fault Code: F18056

Message

[FSM:STAGE:FAILED|RETRY]: Apply configuration to physical end-points.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 18056

mibFaultName: fsmStFailSmLogicalDeviceConfigureApplyConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmStFailSmLogicalDeviceConfigure:AutoConfig

Fault Code: F18056

Message

[FSM:STAGE:FAILED|RETRY]: Auto configure external port link.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:AutoConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: auto-config-failed

mibFaultCode: 18056

mibFaultName: fsmStFailSmLogicalDeviceConfigureAutoConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmStFailSmLogicalDeviceConfigure:CheckConfigIssues

Fault Code: F18056

Message

[FSM:STAGE:FAILED|RETRY]: Check logical device configuration issues.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:CheckConfigIssues)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-config-issues-failed

mibFaultCode: 18056

mibFaultName: fsmStFailSmLogicalDeviceConfigureCheckConfigIssues

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmStFailSmLogicalDeviceConfigure:ResolvePolicy

Fault Code: F18056

Message

[FSM:STAGE:FAILED|RETRY]: Resolve policy and external MO reference.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ResolvePolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-policy-failed

mibFaultCode: 18056

mibFaultName: fsmStFailSmLogicalDeviceConfigureResolvePolicy

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmStFailSmLogicalDeviceConfigure:ValidateLDConfig

Fault Code: F18056

Message

[FSM:STAGE:FAILED|RETRY]: Validate logical device configuration.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ValidateLDConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validateldconfig-failed

mibFaultCode: 18056

mibFaultName: fsmStFailSmLogicalDeviceConfigureValidateLDConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmStFailSdLduUpdateInterfaceStatus:SendStatus

Fault Code: F18058

Message

[FSM:STAGE:FAILED|RETRY]: Send Interface Operational State(FSM-STAGE:sam:dme:SdLduUpdateInterfaceStatus:SendStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-status-failed

mibFaultCode: 18058

mibFaultName: fsmStFailSdLduUpdateInterfaceStatusSendStatus

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmStFailSdLogicalDeviceConfigureUserMacs:ConfigureSwitch

Fault Code: F18059

Message

[FSM:STAGE:FAILED|RETRY]: Invoke Port API to configure the switch(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureUserMacs:ConfigureSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-switch-failed

mibFaultCode: 18059

mibFaultName: fsmStFailSdLogicalDeviceConfigureUserMacsConfigureSwitch

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailSdLogicalDeviceConfigureUserMacs:WaitForSwitchConfig

Fault Code: F18059

Message

[FSM:STAGE:FAILED|RETRY]: Wait for Switch configuration to complete(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureUserMacs:WaitForSwitchConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-config-failed

mibFaultCode: 18059

mibFaultName: fsmStFailSdLogicalDeviceConfigureUserMacsWaitForSwitchConfig

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmStFailEquipmentChassisRebootChassis:ApplyReboot

Fault Code: F18060

Message

[FSM:STAGE:FAILED|RETRY]: Reboot Chassis(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:ApplyReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-reboot-failed

mibFaultCode: 18060

mibFaultName: fsmStFailEquipmentChassisRebootChassisApplyReboot

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRebootChassis:DebundlePort

Fault Code: F18060

Message

[FSM:STAGE:FAILED|RETRY]: Debundle the ports(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 18060

mibFaultName: fsmStFailEquipmentChassisRebootChassisDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRebootChassis:PollDebundlePort

Fault Code: F18060

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 18060

mibFaultName: fsmStFailEquipmentChassisRebootChassisPollDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRebootChassis:ShutdownBlade

Fault Code: F18060

Message

[FSM:STAGE:FAILED|RETRY]: Shutdown Blade(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:ShutdownBlade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-blade-failed

mibFaultCode: 18060

mibFaultName: fsmStFailEquipmentChassisRebootChassisShutdownBlade

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailEquipmentChassisRebootChassis:WaitForBladeShutdown

Fault Code: F18060

Message

[FSM:STAGE:FAILED|RETRY]: Waiting for blade shutdown(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:WaitForBladeShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-shutdown-failed

mibFaultCode: 18060

mibFaultName: fsmStFailEquipmentChassisRebootChassisWaitForBladeShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmStFailFirmwareValidationStatusValidate:CheckReadiness

Fault Code: F18064

Message

[FSM:STAGE:FAILED|RETRY]: Image validation queued(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:CheckReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-readiness-failed

mibFaultCode: 18064

mibFaultName: fsmStFailFirmwareValidationStatusValidateCheckReadiness

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmStFailFirmwareValidationStatusValidate:Complete

Fault Code: F18064

Message

[FSM:STAGE:FAILED|RETRY]: Complete Validation(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:Complete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: complete-failed

mibFaultCode: 18064

mibFaultName: fsmStFailFirmwareValidationStatusValidateComplete

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmStFailFirmwareValidationStatusValidate:PlatformPack

Fault Code: F18064

Message

[FSM:STAGE:FAILED|RETRY]: Validating the platform pack(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:PlatformPack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: platform-pack-failed

mibFaultCode: 18064

mibFaultName: fsmStFailFirmwareValidationStatusValidatePlatformPack

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmStFailSdPortsBundleBundleDataPorts:ConfigureLinks

Fault Code: F18081

Message

[FSM:STAGE:FAILED|RETRY]: Trigger ConfigureLinks FSM(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:ConfigureLinks)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-links-failed

mibFaultCode: 18081

mibFaultName: fsmStFailSdPortsBundleBundleDataPortsConfigureLinks

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmStFailSdPortsBundleBundleDataPorts:SendBundleStatus

Fault Code: F18081

Message

[FSM:STAGE:FAILED|RETRY]: Notify Application about Port Bundle Status(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:SendBundleStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bundle-status-failed

mibFaultCode: 18081

mibFaultName: fsmStFailSdPortsBundleBundleDataPortsSendBundleStatus

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmStFailSdPortsBundleBundleDataPorts:UpdateBundleStatus

Fault Code: F18081

Message

[FSM:STAGE:FAILED|RETRY]: Update the bundle status(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:UpdateBundleStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bundle-status-failed

mibFaultCode: 18081

mibFaultName: fsmStFailSdPortsBundleBundleDataPortsUpdateBundleStatus

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmStFailSdPortsBundleBundleDataPorts:WaitForConfigCompletion

Fault Code: F18081

Message

[FSM:STAGE:FAILED|RETRY]: Wait for links configuration completion(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:WaitForConfigCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-config-completion-failed

mibFaultCode: 18081

mibFaultName: fsmStFailSdPortsBundleBundleDataPortsWaitForConfigCompletion

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmStFailSdHotfixInstallHotfix:Install

Fault Code: F18082

Message

[FSM:STAGE:FAILED|RETRY]: Install hotfix(FSM-STAGE:sam:dme:SdHotfixInstallHotfix:Install)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: install-failed

mibFaultCode: 18082

mibFaultName: fsmStFailSdHotfixInstallHotfixInstall

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmStFailSdHotfixInstallHotfix:UpdateHotfix

Fault Code: F18082

Message

[FSM:STAGE:FAILED|RETRY]: Updates the state of hotifx(FSM-STAGE:sam:dme:SdHotfixInstallHotfix:UpdateHotfix)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-hotfix-failed

mibFaultCode: 18082

mibFaultName: fsmStFailSdHotfixInstallHotfixUpdateHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmStFailSdHotfixUninstallHotfix:Uninstall

Fault Code: F18083

Message

[FSM:STAGE:FAILED|RETRY]: Uninstall hotfix(FSM-STAGE:sam:dme:SdHotfixUninstallHotfix:Uninstall)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: uninstall-failed

mibFaultCode: 18083

mibFaultName: fsmStFailSdHotfixUninstallHotfixUninstall

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmStFailSdHotfixUninstallHotfix:UpdateHotfix

Fault Code: F18083

Message

[FSM:STAGE:FAILED|RETRY]: Updates the state of hotifx(FSM-STAGE:sam:dme:SdHotfixUninstallHotfix:UpdateHotfix)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-hotfix-failed

mibFaultCode: 18083

mibFaultName: fsmStFailSdHotfixUninstallHotfixUpdateHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmRmtErrEquipmentChassisRemoveChassis:DisableEndPoint

Fault Code: F77847

Message

[FSM:STAGE:REMOTE-ERROR]: unconfiguring access to chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:DisableEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-end-point-failed

mibFaultCode: 77847

mibFaultName: fsmRmtErrEquipmentChassisRemoveChassisDisableEndPoint

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRemoveChassis:UnIdentifyLocal

Fault Code: F77847

Message

[FSM:STAGE:REMOTE-ERROR]: erasing chassis identity [id] from primary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-local-failed

mibFaultCode: 77847

mibFaultName: fsmRmtErrEquipmentChassisRemoveChassisUnIdentifyLocal

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRemoveChassis:UnIdentifyPeer

Fault Code: F77847

Message

[FSM:STAGE:REMOTE-ERROR]: erasing chassis identity [id] from secondary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-peer-failed

mibFaultCode: 77847

mibFaultName: fsmRmtErrEquipmentChassisRemoveChassisUnIdentifyPeer

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRemoveChassis:Wait

Fault Code: F77847

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 77847

mibFaultName: fsmRmtErrEquipmentChassisRemoveChassisWait

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRemoveChassis:decomission

Fault Code: F77847

Message

[FSM:STAGE:REMOTE-ERROR]: decomissioning chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:decomission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: decomission-failed

mibFaultCode: 77847

mibFaultName: fsmRmtErrEquipmentChassisRemoveChassisDecomission

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentLocatorLedSetLocatorLed:Execute

Fault Code: F77848

Message

[FSM:STAGE:REMOTE-ERROR]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 77848

mibFaultName: fsmRmtErrEquipmentLocatorLedSetLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmRmtErrMgmtControllerExtMgmtIfConfig:Primary

Fault Code: F77958

Message

[FSM:STAGE:REMOTE-ERROR]: external mgmt interface configuration on primary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Primary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: primary-failed

mibFaultCode: 77958

mibFaultName: fsmRmtErrMgmtControllerExtMgmtIfConfigPrimary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerExtMgmtIfConfig:Secondary

Fault Code: F77958

Message

[FSM:STAGE:REMOTE-ERROR]: external mgmt interface configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Secondary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: secondary-failed

mibFaultCode: 77958

mibFaultName: fsmRmtErrMgmtControllerExtMgmtIfConfigSecondary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrFabricComputeSlotEpIdentify:ExecuteLocal

Fault Code: F77959

Message

[FSM:STAGE:REMOTE-ERROR]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 77959

mibFaultName: fsmRmtErrFabricComputeSlotEpIdentifyExecuteLocal

moClass: fabric:ComputeSlotEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fsmRmtErrFabricComputeSlotEpIdentify:ExecutePeer

Fault Code: F77959

Message

[FSM:STAGE:REMOTE-ERROR]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 77959

mibFaultName: fsmRmtErrFabricComputeSlotEpIdentifyExecutePeer

moClass: fabric:ComputeSlotEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fsmRmtErrComputeBladeDiscover:BiosPostCompletion

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBiosPostCompletion

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BladeBootPnuos

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: power server [chassisId]/[slotId] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-pnuos-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBladeBootPnuos

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BladeBootWait

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-wait-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBladeBootWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BladePowerOn

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: power on server [chassisId]/[slotId] for discovery(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBladePowerOn

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BladeReadSmbios

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for SMBIOS table from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-read-smbios-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBladeReadSmbios

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcConfigPnuOS

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcConfigPnuOS

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcInventory

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcPreConfigPnuOSLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-pre-config-pnuoslocal-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcPreConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcPreConfigPnuOSPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-pre-config-pnuospeer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcPreConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcPresence

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcPresence

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:BmcShutdownDiscovered

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown the server [chassisId]/[slotId]; deep discovery completed(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcShutdownDiscovered)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-discovered-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverBmcShutdownDiscovered

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:CheckPowerAvailability

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverCheckPowerAvailability

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:ConfigBMCPowerParams

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring power profiling parameters for server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigBMCPowerParams)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configbmcpower-params-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverConfigBMCPowerParams

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:ConfigFeLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-local-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:ConfigFePeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-peer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:ConfigFlexFlashScrub

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring FlexFlash Scrub on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverConfigFlexFlashScrub

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:ConfigUserAccess

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverConfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:HandlePooling

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Invoke post-discovery policies on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverHandlePooling

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicConfigPnuOSLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configure primary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicConfigPnuOSPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configure secondary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicPresenceLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresenceLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-local-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicPresenceLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicPresencePeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresencePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-peer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicPresencePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicUnconfigPnuOSLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicUnconfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:NicUnconfigPnuOSPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverNicUnconfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:OobStorageInventory

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Perform oob storage inventory of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverOobStorageInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSCatalog

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSCatalog

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSIdent

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSIdent

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSInventory

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Perform inventory of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSPolicy

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSPolicy

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSPowerProfiling

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Profile power for server [chassisId]/[slotId] by running benchmark(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSPowerProfiling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospower-profiling-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSPowerProfiling

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSScrub

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Scrub server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSScrub

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PnuOSSelfTest

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger self-test of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPnuOSSelfTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PowerDeployWait

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPowerDeployWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PreSanitize

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPreSanitize

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:PrepareKeyFile

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:ComputeBladeDiscover:PrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-key-file-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverPrepareKeyFile

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:Sanitize

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSanitize

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SendBmcProfilingDone

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for valid power profile for server [chassisId]/[slotId] from CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:SendBmcProfilingDone)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bmc-profiling-done-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSendBmcProfilingDone

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SendBmcProfilingInit

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Start profiling power for server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:SendBmcProfilingInit)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bmc-profiling-init-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSendBmcProfilingInit

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SetupVmediaLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-local-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSetupVmediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SetupVmediaPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-peer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSetupVmediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SolRedirectDisable

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSolRedirectDisable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SolRedirectEnable

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSolRedirectEnable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SwConfigPnuOSLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configure primary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSwConfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SwConfigPnuOSPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: configure secondary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSwConfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SwUnconfigPnuOSLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSwUnconfigPnuOSLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:SwUnconfigPnuOSPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSwUnconfigPnuOSPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:TeardownVmediaLocal

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the Virtual Media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-local-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverTeardownVmediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:TeardownVmediaPeer

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the Virtual media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-peer-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverTeardownVmediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:UnconfigCimcVMedia

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverUnconfigCimcVMedia

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:UnconfigExtMgmtGw

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverUnconfigExtMgmtGw

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:UnconfigExtMgmtRules

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputeBladeDiscover:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverUnconfigExtMgmtRules

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:hagConnect

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-connect-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverHagConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:hagDisconnect

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-disconnect-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverHagDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:serialDebugConnect

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSerialDebugConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiscover:serialDebugDisconnect

Fault Code: F77960

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 77960

mibFaultName: fsmRmtErrComputeBladeDiscoverSerialDebugDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrEquipmentChassisPsuPolicyConfig:Execute

Fault Code: F77973

Message

[FSM:STAGE:REMOTE-ERROR]: Deploying Power Management policy changes on chassis [id](FSM-STAGE:sam:dme:EquipmentChassisPsuPolicyConfig:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 77973

mibFaultName: fsmRmtErrEquipmentChassisPsuPolicyConfigExecute

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrAdaptorHostFcIfResetFcPersBinding:ExecuteLocal

Fault Code: F77974

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 77974

mibFaultName: fsmRmtErrAdaptorHostFcIfResetFcPersBindingExecuteLocal

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrAdaptorHostFcIfResetFcPersBinding:ExecutePeer

Fault Code: F77974

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 77974

mibFaultName: fsmRmtErrAdaptorHostFcIfResetFcPersBindingExecutePeer

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrComputeBladeDiag:BiosPostCompletion

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBiosPostCompletion

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BladeBoot

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Power-on server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBladeBoot

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BladeBootWait

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-boot-wait-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBladeBootWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BladePowerOn

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server [chassisId]/[slotId] for diagnostics(FSM-STAGE:sam:dme:ComputeBladeDiag:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBladePowerOn

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BladeReadSmbios

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Read SMBIOS tables on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-read-smbios-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBladeReadSmbios

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BmcConfigPnuOS

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBmcConfigPnuOS

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BmcInventory

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBmcInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BmcPresence

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBmcPresence

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:BmcShutdownDiagCompleted

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcShutdownDiagCompleted)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-diag-completed-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagBmcShutdownDiagCompleted

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:CleanupServerConnSwA

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning up server [chassisId]/[slotId] interface on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-server-conn-sw-afailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagCleanupServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:CleanupServerConnSwB

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning up server [chassisId]/[slotId] interface on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-server-conn-sw-bfailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagCleanupServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:ConfigFeLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:ConfigFePeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-fe-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:ConfigUserAccess

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagConfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:DebugWait

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for debugging for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DebugWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debug-wait-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagDebugWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:DeriveConfig

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DeriveConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: derive-config-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagDeriveConfig

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:DisableServerConnSwA

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Disable server [chassisId]/[slotId] interface on fabric A after completion of network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-server-conn-sw-afailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagDisableServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:DisableServerConnSwB

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Disable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-server-conn-sw-bfailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagDisableServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:EnableServerConnSwA

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Enable server [chassisId]/[slotId] connectivity on fabric A in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-server-conn-sw-afailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagEnableServerConnSwA

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:EnableServerConnSwB

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Enable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-server-conn-sw-bfailed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagEnableServerConnSwB

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:EvaluateStatus

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Evaluating status; diagnostics completed(FSM-STAGE:sam:dme:ComputeBladeDiag:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagEvaluateStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:FabricATrafficTestStatus

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Gather status of network traffic tests on fabric A for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricATrafficTestStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: fabricatraffic-test-status-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagFabricATrafficTestStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:FabricBTrafficTestStatus

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Gather status of network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricBTrafficTestStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: fabricbtraffic-test-status-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagFabricBTrafficTestStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:GenerateLogWait

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for collection of diagnostic logs from server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateLogWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: generate-log-wait-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagGenerateLogWait

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:GenerateReport

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Generating report for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateReport)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: generate-report-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagGenerateReport

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostCatalog

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Populate diagnostics catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-catalog-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostCatalog

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostConnect

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-connect-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostDisconnect

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect diagnostics environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-disconnect-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostIdent

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Identify diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-ident-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostIdent

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostInventory

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Perform inventory of server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:HostInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-inventory-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostInventory

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostPolicy

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Populate diagnostics environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-policy-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostPolicy

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostServerDiag

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger diagnostics on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiag)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-server-diag-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostServerDiag

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:HostServerDiagStatus

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Diagnostics status on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiagStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-server-diag-status-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagHostServerDiagStatus

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicConfigLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicConfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicConfigPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicConfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicInventoryLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicInventoryLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicInventoryPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicInventoryPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicPresenceLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresenceLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicPresenceLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicPresencePeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresencePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-presence-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicPresencePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicUnconfigLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicUnconfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:NicUnconfigPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagNicUnconfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:RemoveConfig

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-config-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagRemoveConfig

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:RemoveVMediaLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: removevmedia-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagRemoveVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:RemoveVMediaPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: removevmedia-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagRemoveVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:RestoreConfigFeLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Reconfiguring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFeLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-config-fe-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagRestoreConfigFeLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:RestoreConfigFePeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Reconfiguring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-config-fe-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagRestoreConfigFePeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SetDiagUser

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Populate diagnostics environment with a user account to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SetDiagUser)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-diag-user-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSetDiagUser

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SetupVMediaLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setupvmedia-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSetupVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SetupVMediaPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setupvmedia-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSetupVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SolRedirectDisable

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSolRedirectDisable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SolRedirectEnable

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSolRedirectEnable

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:StartFabricATrafficTest

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger network traffic tests on fabric A on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricATrafficTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-fabricatraffic-test-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagStartFabricATrafficTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:StartFabricBTrafficTest

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricBTrafficTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-fabricbtraffic-test-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagStartFabricBTrafficTest

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:StopVMediaLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagStopVMediaLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:StopVMediaPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagStopVMediaPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SwConfigLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configure primary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSwConfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SwConfigPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Configure secondary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSwConfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SwUnconfigLocal

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-local-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSwUnconfigLocal

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:SwUnconfigPeer

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-peer-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSwUnconfigPeer

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:UnconfigUserAccess

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:UnconfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-user-access-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagUnconfigUserAccess

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:serialDebugConnect

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSerialDebugConnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrComputeBladeDiag:serialDebugDisconnect

Fault Code: F77975

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 77975

mibFaultName: fsmRmtErrComputeBladeDiagSerialDebugDisconnect

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmRmtErrFabricLanCloudSwitchMode:SwConfigLocal

Fault Code: F77979

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 77979

mibFaultName: fsmRmtErrFabricLanCloudSwitchModeSwConfigLocal

moClass: fabric:LanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan

fsmRmtErrFabricLanCloudSwitchMode:SwConfigPeer

Fault Code: F77979

Message

[FSM:STAGE:REMOTE-ERROR]: Fabric interconnect mode configuration to primary(FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 77979

mibFaultName: fsmRmtErrFabricLanCloudSwitchModeSwConfigPeer

moClass: fabric:LanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan

fsmRmtErrVnicProfileSetDeploy:Local

Fault Code: F77990

Message

[FSM:STAGE:REMOTE-ERROR]: VNIC profile configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 77990

mibFaultName: fsmRmtErrVnicProfileSetDeployLocal

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmRmtErrVnicProfileSetDeploy:Peer

Fault Code: F77990

Message

[FSM:STAGE:REMOTE-ERROR]: VNIC profile configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 77990

mibFaultName: fsmRmtErrVnicProfileSetDeployPeer

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpSettings

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated settings (eg. timezone)(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpSettings)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-settings-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpSettings

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsLocal

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-local-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsPeer

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-peer-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsLocal

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-adaptors-local-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToAdaptorsLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsPeer

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-adaptors-peer-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToAdaptorsPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomLocal

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-fex-iom-local-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToFexIomLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomPeer

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: propogate-ep-time-zone-settings-to-fex-iom-peer-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpPropogateEpTimeZoneSettingsToFexIomPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:SetEpLocal

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: communication service [name] configuration to primary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-local-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpSetEpLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpUpdateSvcEp:SetEpPeer

Fault Code: F78016

Message

[FSM:STAGE:REMOTE-ERROR]: communication service [name] configuration to secondary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-peer-failed

mibFaultCode: 78016

mibFaultName: fsmRmtErrCommSvcEpUpdateSvcEpSetEpPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpRestartWebSvc:local

Fault Code: F78017

Message

[FSM:STAGE:REMOTE-ERROR]: restart web services in primary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78017

mibFaultName: fsmRmtErrCommSvcEpRestartWebSvcLocal

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrCommSvcEpRestartWebSvc:peer

Fault Code: F78017

Message

[FSM:STAGE:REMOTE-ERROR]: restart web services in secondary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78017

mibFaultName: fsmRmtErrCommSvcEpRestartWebSvcPeer

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmRmtErrAaaEpUpdateEp:SetEpLocal

Fault Code: F78019

Message

[FSM:STAGE:REMOTE-ERROR]: external aaa server configuration to primary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-local-failed

mibFaultCode: 78019

mibFaultName: fsmRmtErrAaaEpUpdateEpSetEpLocal

moClass: aaa:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext

Affected MO: sys/radius-ext

Affected MO: sys/tacacs-ext

fsmRmtErrAaaEpUpdateEp:SetEpPeer

Fault Code: F78019

Message

[FSM:STAGE:REMOTE-ERROR]: external aaa server configuration to secondary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-peer-failed

mibFaultCode: 78019

mibFaultName: fsmRmtErrAaaEpUpdateEpSetEpPeer

moClass: aaa:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext

Affected MO: sys/radius-ext

Affected MO: sys/tacacs-ext

fsmRmtErrAaaRealmUpdateRealm:SetRealmLocal

Fault Code: F78020

Message

[FSM:STAGE:REMOTE-ERROR]: realm configuration to primary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-realm-local-failed

mibFaultCode: 78020

mibFaultName: fsmRmtErrAaaRealmUpdateRealmSetRealmLocal

moClass: aaa:Realm

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm

fsmRmtErrAaaRealmUpdateRealm:SetRealmPeer

Fault Code: F78020

Message

[FSM:STAGE:REMOTE-ERROR]: realm configuration to secondary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-realm-peer-failed

mibFaultCode: 78020

mibFaultName: fsmRmtErrAaaRealmUpdateRealmSetRealmPeer

moClass: aaa:Realm

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm

fsmRmtErrAaaUserEpUpdateUserEp:SetUserLocal

Fault Code: F78021

Message

[FSM:STAGE:REMOTE-ERROR]: user configuration to primary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-user-local-failed

mibFaultCode: 78021

mibFaultName: fsmRmtErrAaaUserEpUpdateUserEpSetUserLocal

moClass: aaa:UserEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext

fsmRmtErrAaaUserEpUpdateUserEp:SetUserPeer

Fault Code: F78021

Message

[FSM:STAGE:REMOTE-ERROR]: user configuration to secondary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-user-peer-failed

mibFaultCode: 78021

mibFaultName: fsmRmtErrAaaUserEpUpdateUserEpSetUserPeer

moClass: aaa:UserEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext

fsmRmtErrPkiEpUpdateEp:PostSetKeyRingLocal

Fault Code: F78022

Message

[FSM:STAGE:REMOTE-ERROR]: post processing after keyring configration on primary(FSM-STAGE:sam:dme:PkiEpUpdateEp:PostSetKeyRingLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: post-set-key-ring-local-failed

mibFaultCode: 78022

mibFaultName: fsmRmtErrPkiEpUpdateEpPostSetKeyRingLocal

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmRmtErrPkiEpUpdateEp:PostSetKeyRingPeer

Fault Code: F78022

Message

[FSM:STAGE:REMOTE-ERROR]: post processing after keyring configuration on secondary(FSM-STAGE:sam:dme:PkiEpUpdateEp:PostSetKeyRingPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: post-set-key-ring-peer-failed

mibFaultCode: 78022

mibFaultName: fsmRmtErrPkiEpUpdateEpPostSetKeyRingPeer

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmRmtErrPkiEpUpdateEp:SetKeyRingLocal

Fault Code: F78022

Message

[FSM:STAGE:REMOTE-ERROR]: keyring configuration on primary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-key-ring-local-failed

mibFaultCode: 78022

mibFaultName: fsmRmtErrPkiEpUpdateEpSetKeyRingLocal

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmRmtErrPkiEpUpdateEp:SetKeyRingPeer

Fault Code: F78022

Message

[FSM:STAGE:REMOTE-ERROR]: keyring configuration on secondary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-key-ring-peer-failed

mibFaultCode: 78022

mibFaultName: fsmRmtErrPkiEpUpdateEpSetKeyRingPeer

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmRmtErrSysfileMutationSingle:Execute

Fault Code: F78040

Message

[FSM:STAGE:REMOTE-ERROR]: [action] file [name](FSM-STAGE:sam:dme:SysfileMutationSingle:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78040

mibFaultName: fsmRmtErrSysfileMutationSingleExecute

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmRmtErrSysfileMutationGlobal:Local

Fault Code: F78041

Message

[FSM:STAGE:REMOTE-ERROR]: remove files from local(FSM-STAGE:sam:dme:SysfileMutationGlobal:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78041

mibFaultName: fsmRmtErrSysfileMutationGlobalLocal

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmRmtErrSysfileMutationGlobal:Peer

Fault Code: F78041

Message

[FSM:STAGE:REMOTE-ERROR]: remove files from peer(FSM-STAGE:sam:dme:SysfileMutationGlobal:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78041

mibFaultName: fsmRmtErrSysfileMutationGlobalPeer

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmRmtErrSysdebugManualCoreFileExportTargetExport:Execute

Fault Code: F78044

Message

[FSM:STAGE:REMOTE-ERROR]: export core file [name] to [hostname](FSM-STAGE:sam:dme:SysdebugManualCoreFileExportTargetExport:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78044

mibFaultName: fsmRmtErrSysdebugManualCoreFileExportTargetExportExecute

moClass: sysdebug:ManualCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/export-to-[hostname]

fsmRmtErrSysdebugAutoCoreFileExportTargetConfigure:Local

Fault Code: F78045

Message

[FSM:STAGE:REMOTE-ERROR]: configuring automatic core file export service on local(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Local)

Explanation

Cisco Firepower Manager could not set the configurations in the primary Fabric Interconnect for auto core transfer to remote TFTP server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78045

mibFaultName: fsmRmtErrSysdebugAutoCoreFileExportTargetConfigureLocal

moClass: sysdebug:AutoCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fsmRmtErrSysdebugAutoCoreFileExportTargetConfigure:Peer

Fault Code: F78045

Message

[FSM:STAGE:REMOTE-ERROR]: configuring automatic core file export service on peer(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Peer)

Explanation

Cisco Firepower Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for auto core transfer to remote TFTP server. This fault typically appears for one of the following reasons:

- The subordinate FI is not reachable.

- The subordinate FI is experiencing an internal system error on applying the configuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FI cluster state to ensure that the subordinate FI is reachable and functioning correctly. If the subordinate FI is down, take appropriate corrective actions so that the Firepower cluster goes into HA ready state.

Step 2 If the HA state of the primary and subordinate FIs are good, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78045

mibFaultName: fsmRmtErrSysdebugAutoCoreFileExportTargetConfigurePeer

moClass: sysdebug:AutoCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fsmRmtErrSysdebugLogControlEpLogControlPersist:Local

Fault Code: F78046

Message

[FSM:STAGE:REMOTE-ERROR]: persisting LogControl on local(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78046

mibFaultName: fsmRmtErrSysdebugLogControlEpLogControlPersistLocal

moClass: sysdebug:LogControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/logcontrol

fsmRmtErrSysdebugLogControlEpLogControlPersist:Peer

Fault Code: F78046

Message

[FSM:STAGE:REMOTE-ERROR]: persisting LogControl on peer(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78046

mibFaultName: fsmRmtErrSysdebugLogControlEpLogControlPersistPeer

moClass: sysdebug:LogControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/logcontrol

fsmRmtErrSwAccessDomainDeploy:UpdateConnectivity

Fault Code: F78074

Message

[FSM:STAGE:REMOTE-ERROR]: internal network configuration on [switchId](FSM-STAGE:sam:dme:SwAccessDomainDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 78074

mibFaultName: fsmRmtErrSwAccessDomainDeployUpdateConnectivity

moClass: sw:AccessDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/access-eth

fsmRmtErrSwEthLanBorderDeploy:UpdateConnectivity

Fault Code: F78075

Message

[FSM:STAGE:REMOTE-ERROR]: Uplink eth port configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 78075

mibFaultName: fsmRmtErrSwEthLanBorderDeployUpdateConnectivity

moClass: sw:EthLanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-eth

fsmRmtErrSwEthLanBorderDeploy:UpdateVlanGroups

Fault Code: F78075

Message

[FSM:STAGE:REMOTE-ERROR]: VLAN group configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateVlanGroups)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-vlan-groups-failed

mibFaultCode: 78075

mibFaultName: fsmRmtErrSwEthLanBorderDeployUpdateVlanGroups

moClass: sw:EthLanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-eth

fsmRmtErrSwFcSanBorderDeploy:UpdateConnectivity

Fault Code: F78076

Message

[FSM:STAGE:REMOTE-ERROR]: Uplink fc port configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 78076

mibFaultName: fsmRmtErrSwFcSanBorderDeployUpdateConnectivity

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmRmtErrSwUtilityDomainDeploy:UpdateConnectivity

Fault Code: F78077

Message

[FSM:STAGE:REMOTE-ERROR]: Utility network configuration on [switchId](FSM-STAGE:sam:dme:SwUtilityDomainDeploy:UpdateConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-connectivity-failed

mibFaultCode: 78077

mibFaultName: fsmRmtErrSwUtilityDomainDeployUpdateConnectivity

moClass: sw:UtilityDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/utility-eth

fsmRmtErrSyntheticFsObjCreate:createLocal

Fault Code: F78081

Message

[FSM:STAGE:REMOTE-ERROR]: create on primary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: create-local-failed

mibFaultCode: 78081

mibFaultName: fsmRmtErrSyntheticFsObjCreateCreateLocal

moClass: synthetic:FsObj

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/file-[name]

fsmRmtErrSyntheticFsObjCreate:createRemote

Fault Code: F78081

Message

[FSM:STAGE:REMOTE-ERROR]: create on secondary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: create-remote-failed

mibFaultCode: 78081

mibFaultName: fsmRmtErrSyntheticFsObjCreateCreateRemote

moClass: synthetic:FsObj

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/file-[name]

fsmRmtErrFirmwareDownloaderDownload:CopyRemote

Fault Code: F78090

Message

[FSM:STAGE:REMOTE-ERROR]: sync images to subordinate(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78090

mibFaultName: fsmRmtErrFirmwareDownloaderDownloadCopyRemote

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmRmtErrFirmwareDownloaderDownload:DeleteLocal

Fault Code: F78090

Message

[FSM:STAGE:REMOTE-ERROR]: deleting downloadable [fileName] on local(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 78090

mibFaultName: fsmRmtErrFirmwareDownloaderDownloadDeleteLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmRmtErrFirmwareDownloaderDownload:Local

Fault Code: F78090

Message

[FSM:STAGE:REMOTE-ERROR]: downloading image or file [fileName] from [server](FSM-STAGE:sam:dme:FirmwareDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78090

mibFaultName: fsmRmtErrFirmwareDownloaderDownloadLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmRmtErrFirmwareDownloaderDownload:UnpackLocal

Fault Code: F78090

Message

[FSM:STAGE:REMOTE-ERROR]: unpacking image [fileName] on primary(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 78090

mibFaultName: fsmRmtErrFirmwareDownloaderDownloadUnpackLocal

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmRmtErrFirmwareImageDelete:Local

Fault Code: F78091

Message

[FSM:STAGE:REMOTE-ERROR]: deleting image file [name] ([invTag]) from primary(FSM-STAGE:sam:dme:FirmwareImageDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78091

mibFaultName: fsmRmtErrFirmwareImageDeleteLocal

moClass: firmware:Image

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/image-[name]

Affected MO: sys/fw-catalogue/image-[name]

fsmRmtErrFirmwareImageDelete:Remote

Fault Code: F78091

Message

[FSM:STAGE:REMOTE-ERROR]: deleting image file [name] ([invTag]) from secondary(FSM-STAGE:sam:dme:FirmwareImageDelete:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78091

mibFaultName: fsmRmtErrFirmwareImageDeleteRemote

moClass: firmware:Image

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/image-[name]

Affected MO: sys/fw-catalogue/image-[name]

fsmRmtErrMgmtControllerUpdateSwitch:copyToLocal

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-to-local-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchCopyToLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:copyToPeer

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-to-peer-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchCopyToPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:resetLocal

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: rebooting local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-local-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchResetLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:resetRemote

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: rebooting remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-remote-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchResetRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:updateLocal

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: updating local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-local-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchUpdateLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:updateRemote

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: updating peer fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-remote-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchUpdateRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:verifyLocal

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: verifying boot variables for local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-local-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchVerifyLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateSwitch:verifyRemote

Fault Code: F78093

Message

[FSM:STAGE:REMOTE-ERROR]: verifying boot variables for remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-remote-failed

mibFaultCode: 78093

mibFaultName: fsmRmtErrMgmtControllerUpdateSwitchVerifyRemote

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateIOM:CopyIOMImgToSub

Fault Code: F78094

Message

[FSM:STAGE:REMOTE-ERROR]: Copying IOM Image to subordinate FI(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:CopyIOMImgToSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copyiomimg-to-sub-failed

mibFaultCode: 78094

mibFaultName: fsmRmtErrMgmtControllerUpdateIOMCopyIOMImgToSub

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateIOM:CopyImgFromRep

Fault Code: F78094

Message

[FSM:STAGE:REMOTE-ERROR]: Copying IOM Image from repository to FI(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:CopyImgFromRep)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-img-from-rep-failed

mibFaultCode: 78094

mibFaultName: fsmRmtErrMgmtControllerUpdateIOMCopyImgFromRep

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateIOM:PollUpdateStatus

Fault Code: F78094

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for IOM update(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 78094

mibFaultName: fsmRmtErrMgmtControllerUpdateIOMPollUpdateStatus

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateIOM:UpdateRequest

Fault Code: F78094

Message

[FSM:STAGE:REMOTE-ERROR]: sending update request to IOM(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 78094

mibFaultName: fsmRmtErrMgmtControllerUpdateIOMUpdateRequest

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerActivateIOM:Activate

Fault Code: F78095

Message

[FSM:STAGE:REMOTE-ERROR]: activating backup image of IOM(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 78095

mibFaultName: fsmRmtErrMgmtControllerActivateIOMActivate

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerActivateIOM:Reset

Fault Code: F78095

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting IOM to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 78095

mibFaultName: fsmRmtErrMgmtControllerActivateIOMReset

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateBMC:PollUpdateStatus

Fault Code: F78096

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for update to complete(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 78096

mibFaultName: fsmRmtErrMgmtControllerUpdateBMCPollUpdateStatus

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateBMC:UpdateRequest

Fault Code: F78096

Message

[FSM:STAGE:REMOTE-ERROR]: sending update request to CIMC(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 78096

mibFaultName: fsmRmtErrMgmtControllerUpdateBMCUpdateRequest

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerActivateBMC:Activate

Fault Code: F78097

Message

[FSM:STAGE:REMOTE-ERROR]: activating backup image of CIMC(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 78097

mibFaultName: fsmRmtErrMgmtControllerActivateBMCActivate

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerActivateBMC:Reset

Fault Code: F78097

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting CIMC to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 78097

mibFaultName: fsmRmtErrMgmtControllerActivateBMCReset

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrCallhomeEpConfigCallhome:SetLocal

Fault Code: F78110

Message

[FSM:STAGE:REMOTE-ERROR]: call-home configuration on primary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78110

mibFaultName: fsmRmtErrCallhomeEpConfigCallhomeSetLocal

moClass: callhome:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fsmRmtErrCallhomeEpConfigCallhome:SetPeer

Fault Code: F78110

Message

[FSM:STAGE:REMOTE-ERROR]: call-home configuration on secondary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78110

mibFaultName: fsmRmtErrCallhomeEpConfigCallhomeSetPeer

moClass: callhome:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fsmRmtErrMgmtIfSwMgmtOobIfConfig:Switch

Fault Code: F78113

Message

[FSM:STAGE:REMOTE-ERROR]: configuring the out-of-band interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtOobIfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 78113

mibFaultName: fsmRmtErrMgmtIfSwMgmtOobIfConfigSwitch

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfSwMgmtInbandIfConfig:Switch

Fault Code: F78114

Message

[FSM:STAGE:REMOTE-ERROR]: configuring the inband interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtInbandIfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 78114

mibFaultName: fsmRmtErrMgmtIfSwMgmtInbandIfConfigSwitch

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfVirtualIfConfig:Local

Fault Code: F78119

Message

[FSM:STAGE:REMOTE-ERROR]: Updating virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78119

mibFaultName: fsmRmtErrMgmtIfVirtualIfConfigLocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfVirtualIfConfig:Remote

Fault Code: F78119

Message

[FSM:STAGE:REMOTE-ERROR]: Updating virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78119

mibFaultName: fsmRmtErrMgmtIfVirtualIfConfigRemote

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfEnableVip:Local

Fault Code: F78120

Message

[FSM:STAGE:REMOTE-ERROR]: Enable virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfEnableVip:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78120

mibFaultName: fsmRmtErrMgmtIfEnableVipLocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfDisableVip:Peer

Fault Code: F78121

Message

[FSM:STAGE:REMOTE-ERROR]: Disable virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfDisableVip:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78121

mibFaultName: fsmRmtErrMgmtIfDisableVipPeer

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtIfEnableHA:Local

Fault Code: F78122

Message

[FSM:STAGE:REMOTE-ERROR]: Transition from single to cluster mode(FSM-STAGE:sam:dme:MgmtIfEnableHA:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78122

mibFaultName: fsmRmtErrMgmtIfEnableHALocal

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmRmtErrMgmtBackupBackup:backupLocal

Fault Code: F78123

Message

[FSM:STAGE:REMOTE-ERROR]: internal database backup(FSM-STAGE:sam:dme:MgmtBackupBackup:backupLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: backup-local-failed

mibFaultCode: 78123

mibFaultName: fsmRmtErrMgmtBackupBackupBackupLocal

moClass: mgmt:Backup

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/backup-[hostname]

fsmRmtErrMgmtBackupBackup:upload

Fault Code: F78123

Message

[FSM:STAGE:REMOTE-ERROR]: internal system backup(FSM-STAGE:sam:dme:MgmtBackupBackup:upload)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upload-failed

mibFaultCode: 78123

mibFaultName: fsmRmtErrMgmtBackupBackupUpload

moClass: mgmt:Backup

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/backup-[hostname]

fsmRmtErrMgmtImporterImport:cleanUp

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning up old Security Service configuration(FSM-STAGE:sam:dme:MgmtImporterImport:cleanUp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clean-up-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportCleanUp

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrMgmtImporterImport:config

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: importing the configuration file(FSM-STAGE:sam:dme:MgmtImporterImport:config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportConfig

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrMgmtImporterImport:configBreakout

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: updating breakout port configuration(FSM-STAGE:sam:dme:MgmtImporterImport:configBreakout)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-breakout-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportConfigBreakout

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrMgmtImporterImport:downloadLocal

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: downloading the configuration file(FSM-STAGE:sam:dme:MgmtImporterImport:downloadLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-local-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportDownloadLocal

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrMgmtImporterImport:reportResults

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: Reporting results of import configuration(FSM-STAGE:sam:dme:MgmtImporterImport:reportResults)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-results-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportReportResults

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrMgmtImporterImport:waitForSwitch

Fault Code: F78124

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for completion of switch configuration(FSM-STAGE:sam:dme:MgmtImporterImport:waitForSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-failed

mibFaultCode: 78124

mibFaultName: fsmRmtErrMgmtImporterImportWaitForSwitch

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmRmtErrStatsCollectionPolicyUpdateEp:SetEpA

Fault Code: F78182

Message

[FSM:STAGE:REMOTE-ERROR]: Update endpoint on fabric interconnect A(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-afailed

mibFaultCode: 78182

mibFaultName: fsmRmtErrStatsCollectionPolicyUpdateEpSetEpA

moClass: stats:CollectionPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: stats/coll-policy-[name]

fsmRmtErrStatsCollectionPolicyUpdateEp:SetEpB

Fault Code: F78182

Message

[FSM:STAGE:REMOTE-ERROR]: Update endpoint on fabric interconnect B(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-ep-bfailed

mibFaultCode: 78182

mibFaultName: fsmRmtErrStatsCollectionPolicyUpdateEpSetEpB

moClass: stats:CollectionPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: stats/coll-policy-[name]

fsmRmtErrQosclassDefinitionConfigGlobalQoS:SetLocal

Fault Code: F78185

Message

[FSM:STAGE:REMOTE-ERROR]: QoS Classification Definition [name] configuration on primary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78185

mibFaultName: fsmRmtErrQosclassDefinitionConfigGlobalQoSSetLocal

moClass: qosclass:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/classes

fsmRmtErrQosclassDefinitionConfigGlobalQoS:SetPeer

Fault Code: F78185

Message

[FSM:STAGE:REMOTE-ERROR]: QoS Classification Definition [name] configuration on secondary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78185

mibFaultName: fsmRmtErrQosclassDefinitionConfigGlobalQoSSetPeer

moClass: qosclass:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/classes

fsmRmtErrEpqosDefinitionDeploy:Local

Fault Code: F78189

Message

[FSM:STAGE:REMOTE-ERROR]: vnic qos policy [name] configuration to primary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78189

mibFaultName: fsmRmtErrEpqosDefinitionDeployLocal

moClass: epqos:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-[name]

fsmRmtErrEpqosDefinitionDeploy:Peer

Fault Code: F78189

Message

[FSM:STAGE:REMOTE-ERROR]: vnic qos policy [name] configuration to secondary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78189

mibFaultName: fsmRmtErrEpqosDefinitionDeployPeer

moClass: epqos:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-[name]

fsmRmtErrEpqosDefinitionDelTaskRemove:Local

Fault Code: F78190

Message

[FSM:STAGE:REMOTE-ERROR]: vnic qos policy [name] removal from primary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78190

mibFaultName: fsmRmtErrEpqosDefinitionDelTaskRemoveLocal

moClass: epqos:DefinitionDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-deletion-[defIntId]

fsmRmtErrEpqosDefinitionDelTaskRemove:Peer

Fault Code: F78190

Message

[FSM:STAGE:REMOTE-ERROR]: vnic qos policy [name] removal from secondary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78190

mibFaultName: fsmRmtErrEpqosDefinitionDelTaskRemovePeer

moClass: epqos:DefinitionDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-deletion-[defIntId]

fsmRmtErrEquipmentIOCardResetCmc:Execute

Fault Code: F78243

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting Chassis Management Controller on IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardResetCmc:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78243

mibFaultName: fsmRmtErrEquipmentIOCardResetCmcExecute

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrMgmtControllerUpdateUCSManager:copyExtToLocal

Fault Code: F78255

Message

[FSM:STAGE:REMOTE-ERROR]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-ext-to-local-failed

mibFaultCode: 78255

mibFaultName: fsmRmtErrMgmtControllerUpdateUCSManagerCopyExtToLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateUCSManager:copyExtToPeer

Fault Code: F78255

Message

[FSM:STAGE:REMOTE-ERROR]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-ext-to-peer-failed

mibFaultCode: 78255

mibFaultName: fsmRmtErrMgmtControllerUpdateUCSManagerCopyExtToPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateUCSManager:execute

Fault Code: F78255

Message

[FSM:STAGE:REMOTE-ERROR]: Updating FPR Manager firmware(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78255

mibFaultName: fsmRmtErrMgmtControllerUpdateUCSManagerExecute

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerUpdateUCSManager:start

Fault Code: F78255

Message

[FSM:STAGE:REMOTE-ERROR]: Scheduling FPR manager update(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 78255

mibFaultName: fsmRmtErrMgmtControllerUpdateUCSManagerStart

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerSysConfig:Primary

Fault Code: F78263

Message

[FSM:STAGE:REMOTE-ERROR]: system configuration on primary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Primary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: primary-failed

mibFaultCode: 78263

mibFaultName: fsmRmtErrMgmtControllerSysConfigPrimary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerSysConfig:Secondary

Fault Code: F78263

Message

[FSM:STAGE:REMOTE-ERROR]: system configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Secondary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: secondary-failed

mibFaultCode: 78263

mibFaultName: fsmRmtErrMgmtControllerSysConfigSecondary

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrAdaptorExtEthIfPathReset:Disable

Fault Code: F78292

Message

[FSM:STAGE:REMOTE-ERROR]: Disable path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Disable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-failed

mibFaultCode: 78292

mibFaultName: fsmRmtErrAdaptorExtEthIfPathResetDisable

moClass: adaptor:ExtEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fsmRmtErrAdaptorExtEthIfPathReset:Enable

Fault Code: F78292

Message

[FSM:STAGE:REMOTE-ERROR]: Enabe path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Enable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-failed

mibFaultCode: 78292

mibFaultName: fsmRmtErrAdaptorExtEthIfPathResetEnable

moClass: adaptor:ExtEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fsmRmtErrAdaptorHostEthIfCircuitReset:DisableA

Fault Code: F78297

Message

[FSM:STAGE:REMOTE-ERROR]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-afailed

mibFaultCode: 78297

mibFaultName: fsmRmtErrAdaptorHostEthIfCircuitResetDisableA

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmRmtErrAdaptorHostEthIfCircuitReset:DisableB

Fault Code: F78297

Message

[FSM:STAGE:REMOTE-ERROR]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-bfailed

mibFaultCode: 78297

mibFaultName: fsmRmtErrAdaptorHostEthIfCircuitResetDisableB

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmRmtErrAdaptorHostEthIfCircuitReset:EnableA

Fault Code: F78297

Message

[FSM:STAGE:REMOTE-ERROR]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-afailed

mibFaultCode: 78297

mibFaultName: fsmRmtErrAdaptorHostEthIfCircuitResetEnableA

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmRmtErrAdaptorHostEthIfCircuitReset:EnableB

Fault Code: F78297

Message

[FSM:STAGE:REMOTE-ERROR]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-bfailed

mibFaultCode: 78297

mibFaultName: fsmRmtErrAdaptorHostEthIfCircuitResetEnableB

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmRmtErrAdaptorHostFcIfCircuitReset:DisableA

Fault Code: F78298

Message

[FSM:STAGE:REMOTE-ERROR]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-afailed

mibFaultCode: 78298

mibFaultName: fsmRmtErrAdaptorHostFcIfCircuitResetDisableA

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrAdaptorHostFcIfCircuitReset:DisableB

Fault Code: F78298

Message

[FSM:STAGE:REMOTE-ERROR]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: disable-bfailed

mibFaultCode: 78298

mibFaultName: fsmRmtErrAdaptorHostFcIfCircuitResetDisableB

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrAdaptorHostFcIfCircuitReset:EnableA

Fault Code: F78298

Message

[FSM:STAGE:REMOTE-ERROR]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-afailed

mibFaultCode: 78298

mibFaultName: fsmRmtErrAdaptorHostFcIfCircuitResetEnableA

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrAdaptorHostFcIfCircuitReset:EnableB

Fault Code: F78298

Message

[FSM:STAGE:REMOTE-ERROR]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-bfailed

mibFaultCode: 78298

mibFaultName: fsmRmtErrAdaptorHostFcIfCircuitResetEnableB

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmRmtErrExtvmmProviderConfig:GetVersion

Fault Code: F78319

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager version fetch(FSM-STAGE:sam:dme:ExtvmmProviderConfig:GetVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: get-version-failed

mibFaultCode: 78319

mibFaultName: fsmRmtErrExtvmmProviderConfigGetVersion

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmRmtErrExtvmmProviderConfig:SetLocal

Fault Code: F78319

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78319

mibFaultName: fsmRmtErrExtvmmProviderConfigSetLocal

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmRmtErrExtvmmProviderConfig:SetPeer

Fault Code: F78319

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78319

mibFaultName: fsmRmtErrExtvmmProviderConfigSetPeer

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmRmtErrExtvmmKeyStoreCertInstall:SetLocal

Fault Code: F78320

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager cetificate configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78320

mibFaultName: fsmRmtErrExtvmmKeyStoreCertInstallSetLocal

moClass: extvmm:KeyStore

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/key-store

fsmRmtErrExtvmmKeyStoreCertInstall:SetPeer

Fault Code: F78320

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager certificate configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78320

mibFaultName: fsmRmtErrExtvmmKeyStoreCertInstallSetPeer

moClass: extvmm:KeyStore

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/key-store

fsmRmtErrExtvmmSwitchDelTaskRemoveProvider:RemoveLocal

Fault Code: F78321

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager deletion from local fabric(FSM-STAGE:sam:dme:ExtvmmSwitchDelTaskRemoveProvider:RemoveLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-local-failed

mibFaultCode: 78321

mibFaultName: fsmRmtErrExtvmmSwitchDelTaskRemoveProviderRemoveLocal

moClass: extvmm:SwitchDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vsw-deltask-[swIntId]

fsmRmtErrExtvmmMasterExtKeyConfig:SetLocal

Fault Code: F78338

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager extension-key configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78338

mibFaultName: fsmRmtErrExtvmmMasterExtKeyConfigSetLocal

moClass: extvmm:MasterExtKey

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/ext-key

fsmRmtErrExtvmmMasterExtKeyConfig:SetPeer

Fault Code: F78338

Message

[FSM:STAGE:REMOTE-ERROR]: external VM manager extension-key configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78338

mibFaultName: fsmRmtErrExtvmmMasterExtKeyConfigSetPeer

moClass: extvmm:MasterExtKey

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/ext-key

fsmRmtErrCapabilityUpdaterUpdater:Apply

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Apply)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterApply

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:CopyRemote

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: syncing catalog files to subordinate(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterCopyRemote

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:DeleteLocal

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: deleting temp image [fileName] on local(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterDeleteLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:EvaluateStatus

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: evaluating status of update(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterEvaluateStatus

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:Local

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: downloading catalog file [fileName] from [server](FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:RescanImages

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: rescanning image files(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterRescanImages

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrCapabilityUpdaterUpdater:UnpackLocal

Fault Code: F78344

Message

[FSM:STAGE:REMOTE-ERROR]: unpacking catalog file [fileName] on primary(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 78344

mibFaultName: fsmRmtErrCapabilityUpdaterUpdaterUnpackLocal

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmRmtErrFirmwareDistributableDelete:Local

Fault Code: F78346

Message

[FSM:STAGE:REMOTE-ERROR]: deleting package [name] from primary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78346

mibFaultName: fsmRmtErrFirmwareDistributableDeleteLocal

moClass: firmware:Distributable

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]

fsmRmtErrFirmwareDistributableDelete:Remote

Fault Code: F78346

Message

[FSM:STAGE:REMOTE-ERROR]: deleting package [name] from secondary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78346

mibFaultName: fsmRmtErrFirmwareDistributableDeleteRemote

moClass: firmware:Distributable

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncBladeAGLocal

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to local bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-bladeaglocal-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncBladeAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncBladeAGRemote

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to remote bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-bladeagremote-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncBladeAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncHostagentAGLocal

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to local hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-hostagentaglocal-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncHostagentAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncHostagentAGRemote

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to remote hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-hostagentagremote-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncHostagentAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncNicAGLocal

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to local nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-nicaglocal-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncNicAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncNicAGRemote

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to remote nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-nicagremote-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncNicAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncPortAGLocal

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to local portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-portaglocal-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncPortAGLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:SyncPortAGRemote

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Sending capability catalogue [version] to remote portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-portagremote-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueSyncPortAGRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueDeployCatalogue:finalize

Fault Code: F78371

Message

[FSM:STAGE:REMOTE-ERROR]: Finalizing capability catalogue [version] deployment(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:finalize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: finalize-failed

mibFaultCode: 78371

mibFaultName: fsmRmtErrCapabilityCatalogueDeployCatalogueFinalize

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrEquipmentFexRemoveFex:CleanupEntries

Fault Code: F78382

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:CleanupEntries)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-entries-failed

mibFaultCode: 78382

mibFaultName: fsmRmtErrEquipmentFexRemoveFexCleanupEntries

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmRmtErrEquipmentFexRemoveFex:UnIdentifyLocal

Fault Code: F78382

Message

[FSM:STAGE:REMOTE-ERROR]: erasing fex identity [id] from primary(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:UnIdentifyLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-identify-local-failed

mibFaultCode: 78382

mibFaultName: fsmRmtErrEquipmentFexRemoveFexUnIdentifyLocal

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmRmtErrEquipmentFexRemoveFex:Wait

Fault Code: F78382

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 78382

mibFaultName: fsmRmtErrEquipmentFexRemoveFexWait

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmRmtErrEquipmentFexRemoveFex:decomission

Fault Code: F78382

Message

[FSM:STAGE:REMOTE-ERROR]: decomissioning fex [id](FSM-STAGE:sam:dme:EquipmentFexRemoveFex:decomission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: decomission-failed

mibFaultCode: 78382

mibFaultName: fsmRmtErrEquipmentFexRemoveFexDecomission

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmRmtErrEquipmentLocatorLedSetFeLocatorLed:Execute

Fault Code: F78383

Message

[FSM:STAGE:REMOTE-ERROR]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFeLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78383

mibFaultName: fsmRmtErrEquipmentLocatorLedSetFeLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmRmtErrEquipmentChassisPowerCap:Config

Fault Code: F78384

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:EquipmentChassisPowerCap:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 78384

mibFaultName: fsmRmtErrEquipmentChassisPowerCapConfig

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentIOCardMuxOffline:CleanupEntries

Fault Code: F78385

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentIOCardMuxOffline:CleanupEntries)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-entries-failed

mibFaultCode: 78385

mibFaultName: fsmRmtErrEquipmentIOCardMuxOfflineCleanupEntries

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrComputePhysicalAssociate:ActivateBios

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:ActivateBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-bios-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateActivateBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BiosImgUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-img-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBiosImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BiosPostCompletion

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BladePowerOff

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Power off server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBladePowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BmcConfigPnuOS

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BmcPreconfigPnuOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BmcPreconfigPnuOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BmcUnconfigPnuOS

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BootHost

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Boot host OS for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootHost)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-host-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBootHost

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BootPnuos

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Bring-up pre-boot environment for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:BootWait

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:CheckPowerAvailability

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ClearBiosUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ClearBiosUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-bios-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateClearBiosUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigCimcVMedia

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: configuring mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-cimcvmedia-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigExtMgmtGw

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: configuring ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-ext-mgmt-gw-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigExtMgmtRules

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: configuring ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-ext-mgmt-rules-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigFlexFlash

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigFlexFlash)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigFlexFlash

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigSoL

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring SoL interface on server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigSoL)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-so-lfailed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigUserAccess

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigUserAccess

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:ConfigUuid

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure logical UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-uuid-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateConfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:DeassertResetBypass

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:DeleteCurlDownloadedImages

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Delete images downloaded from operations manager(FSM-STAGE:sam:dme:ComputePhysicalAssociate:DeleteCurlDownloadedImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-curl-downloaded-images-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateDeleteCurlDownloadedImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:GraphicsImageUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update gpu firmware image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:GraphicsImageUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: graphics-image-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateGraphicsImageUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:HbaImgUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HbaImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hba-img-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHbaImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:HostOSConfig

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure host OS components on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosconfig-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHostOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:HostOSIdent

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Identify host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosident-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHostOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:HostOSPolicy

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Upload host agent policy to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostospolicy-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHostOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:HostOSValidate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Validate host OS on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hostosvalidate-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHostOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:LocalDiskFwUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:LocalDiskFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-disk-fw-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateLocalDiskFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:MarkAdapterForReboot

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:MarkAdapterForReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mark-adapter-for-reboot-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateMarkAdapterForReboot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigHostOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-hostoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigHostOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-hostospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigPnuOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigPnuOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigServiceInfraLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-service-infra-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicConfigServiceInfraPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-service-infra-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicConfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicImgUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-img-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicUnconfigPnuOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:NicUnconfigPnuOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:OobStorageInventory

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Perform oob storage inventory with server profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateOobStorageInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSCatalog

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSConfig

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconfig-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSIdent

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSInventory

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSLocalDiskConfig

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure local disk on server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSLocalDiskConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoslocal-disk-config-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSLocalDiskConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSPolicy

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSSelfTest

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSUnloadDrivers

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Unload drivers on server with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSUnloadDrivers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunload-drivers-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSUnloadDrivers

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PnuOSValidate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Pre-boot environment validation for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PollBiosActivateStatus

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-activate-status-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePollBiosActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PollBiosUpdateStatus

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-update-status-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePollBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PollBoardCtrlUpdateStatus

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBoardCtrlUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-board-ctrl-update-status-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePollBoardCtrlUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PollClearBiosUpdateStatus

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollClearBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-bios-update-status-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePollClearBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PowerDeployWait

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PowerOn

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PowerOnPreConfig

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: PowerOn preconfig for server of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerOnPreConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-pre-config-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePowerOnPreConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PreSanitize

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PrepareForBoot

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare server for booting host OS(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PrepareForBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-for-boot-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePrepareForBoot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:PrepareKeyFile

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-key-file-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociatePrepareKeyFile

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:Sanitize

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SolRedirectDisable

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol Redirection on server [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SolRedirectEnable

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token for server [assignedToDn] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:StorageCtlrImgUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:StorageCtlrImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: storage-ctlr-img-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateStorageCtlrImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigHostOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure primary fabric interconnect for server host os (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-hostoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigHostOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure secondary fabric interconnect for server host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-hostospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigPnuOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigPnuOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigPortNivLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigPortNivPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigServiceInfraLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-service-infra-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwConfigServiceInfraPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Configure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-service-infra-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwConfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwUnconfigPnuOSLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SwUnconfigPnuOSPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:SyncPowerState

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Sync power state for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SyncPowerState)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-power-state-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSyncPowerState

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:UnconfigCimcVMedia

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:UnconfigExtMgmtGw

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:UnconfigExtMgmtRules

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:UpdateBiosRequest

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBiosRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bios-request-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateBiosRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:UpdateBoardCtrlRequest

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBoardCtrlRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-board-ctrl-request-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateBoardCtrlRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:VerifyFcZoneConfig

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalAssociate:VerifyFcZoneConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-fc-zone-config-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateVerifyFcZoneConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:activateAdaptorNwFwLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateActivateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:activateAdaptorNwFwPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateActivateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:activateIBMCFw

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateibmcfw-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateActivateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:copyRemote

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Copy images to peer node(FSM-STAGE:sam:dme:ComputePhysicalAssociate:copyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateCopyRemote

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:downloadImages

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Download images from operations manager(FSM-STAGE:sam:dme:ComputePhysicalAssociate:downloadImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-images-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateDownloadImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:hagHostOSConnect

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagHostOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-hostosconnect-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHagHostOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:hagPnuOSConnect

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:hagPnuOSDisconnect

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:resetIBMC

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:resetIBMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resetibmc-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateResetIBMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:serialDebugPnuOSConnect

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:serialDebugPnuOSDisconnect

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:sspUpdateHostPreBoot

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Provisioning a SSP Blade with Firepower related config before boot for host(FSM-STAGE:sam:dme:ComputePhysicalAssociate:sspUpdateHostPreBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: ssp-update-host-pre-boot-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateSspUpdateHostPreBoot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:updateAdaptorNwFwLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:updateAdaptorNwFwPeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:updateIBMCFw

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateibmcfw-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:updateSspOsSoftware

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Request to upgrade software on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateSspOsSoftware)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-ssp-os-software-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateUpdateSspOsSoftware

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-local-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateWaitForAdaptorNwFwUpdateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-peer-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateWaitForAdaptorNwFwUpdatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:waitForIBMCFwUpdate

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForIBMCFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-foribmcfw-update-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateWaitForIBMCFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalAssociate:waitForSspOsUpdateComplete

Fault Code: F78413

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for upgrade complete from server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForSspOsUpdateComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-ssp-os-update-complete-failed

mibFaultCode: 78413

mibFaultName: fsmRmtErrComputePhysicalAssociateWaitForSspOsUpdateComplete

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BiosPostCompletion

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BmcConfigPnuOS

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BmcPreconfigPnuOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BmcPreconfigPnuOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BmcUnconfigPnuOS

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BootPnuos

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Bring-up pre-boot environment on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:BootWait

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:CheckPowerAvailability

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:ConfigBios

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring BIOS Defaults on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-bios-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateConfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:ConfigFlexFlashScrub

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring FlexFlash Scrub on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateConfigFlexFlashScrub

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:ConfigKvmMgmtDefaultSetting

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configure KVM Mgmt to default before ConfigPnuOs(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigKvmMgmtDefaultSetting)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-kvm-mgmt-default-setting-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateConfigKvmMgmtDefaultSetting

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:ConfigUserAccess

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateConfigUserAccess

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:DeassertResetBypass

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:HandlePooling

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Apply post-disassociation policies to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateHandlePooling

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicConfigPnuOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicConfigPnuOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigHostOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-hostoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigHostOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-hostospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigPnuOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigPnuOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigServiceInfraLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure service infra connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigServiceInfraLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-service-infra-local-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigServiceInfraLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:NicUnconfigServiceInfraPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure service infra connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigServiceInfraPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-service-infra-peer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateNicUnconfigServiceInfraPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSCatalog

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSIdent

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSPolicy

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot environment behavior policy to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSScrub

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Scrub server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSScrub

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSSelfTest

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger self-test of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSUnconfig

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure server from service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSUnconfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunconfig-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSUnconfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PnuOSValidate

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Pre-boot environment validate server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PowerDeployWait

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PowerOn

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server for unconfiguration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:PreSanitize

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociatePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:ResetSecureBootConfig

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secure boot configuration(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ResetSecureBootConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-secure-boot-config-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateResetSecureBootConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:Sanitize

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:Shutdown

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SolRedirectDisable

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol redirection on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SolRedirectEnable

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token for server [serverId] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwConfigPnuOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configure primary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwConfigPnuOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Configure secondary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwConfigPortNivLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwConfigPortNivPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwUnconfigHostOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server to primary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-hostoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwUnconfigHostOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwUnconfigHostOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server to secondary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-hostospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwUnconfigHostOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwUnconfigPnuOSLocal

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:SwUnconfigPnuOSPeer

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigBios

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring BIOS Settings and Boot Order of server [serverId] (service profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-bios-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigCimcVMedia

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigExtMgmtGw

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigExtMgmtRules

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigFlexFlash

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigFlexFlash)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-flex-flash-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigFlexFlash

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigSoL

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Removing SoL configuration from server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigSoL)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-so-lfailed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:UnconfigUuid

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Restore original UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-uuid-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateUnconfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:VerifyFcZoneConfig

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:VerifyFcZoneConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-fc-zone-config-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateVerifyFcZoneConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:hagPnuOSConnect

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:hagPnuOSDisconnect

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:serialDebugPnuOSConnect

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDisassociate:serialDebugPnuOSDisconnect

Fault Code: F78414

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 78414

mibFaultName: fsmRmtErrComputePhysicalDisassociateSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalPowerCap:Config

Fault Code: F78415

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring power cap of server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowerCap:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 78415

mibFaultName: fsmRmtErrComputePhysicalPowerCapConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:CleanupCIMC

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning up CIMC configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupCIMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanupcimc-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionCleanupCIMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:CleanupPortConfigLocal

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning up local port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-port-config-local-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionCleanupPortConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:CleanupPortConfigPeer

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning up peer port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-port-config-peer-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionCleanupPortConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:Execute

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Decommissioning server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:StopVMediaLocal

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionStopVMediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:StopVMediaPeer

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionStopVMediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:UnconfigExtMgmtGw

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDecommission:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalDecommission:UnconfigExtMgmtRules

Fault Code: F78416

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalDecommission:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 78416

mibFaultName: fsmRmtErrComputePhysicalDecommissionUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSoftShutdown:Execute

Fault Code: F78417

Message

[FSM:STAGE:REMOTE-ERROR]: Soft shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftShutdown:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78417

mibFaultName: fsmRmtErrComputePhysicalSoftShutdownExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalHardShutdown:Execute

Fault Code: F78418

Message

[FSM:STAGE:REMOTE-ERROR]: Hard shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardShutdown:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78418

mibFaultName: fsmRmtErrComputePhysicalHardShutdownExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalTurnup:Execute

Fault Code: F78419

Message

[FSM:STAGE:REMOTE-ERROR]: Power-on server [dn](FSM-STAGE:sam:dme:ComputePhysicalTurnup:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78419

mibFaultName: fsmRmtErrComputePhysicalTurnupExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalPowercycle:Execute

Fault Code: F78420

Message

[FSM:STAGE:REMOTE-ERROR]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78420

mibFaultName: fsmRmtErrComputePhysicalPowercycleExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalPowercycle:PreSanitize

Fault Code: F78420

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78420

mibFaultName: fsmRmtErrComputePhysicalPowercyclePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalPowercycle:Sanitize

Fault Code: F78420

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78420

mibFaultName: fsmRmtErrComputePhysicalPowercycleSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalHardreset:Execute

Fault Code: F78421

Message

[FSM:STAGE:REMOTE-ERROR]: Hard-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78421

mibFaultName: fsmRmtErrComputePhysicalHardresetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalHardreset:PreSanitize

Fault Code: F78421

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78421

mibFaultName: fsmRmtErrComputePhysicalHardresetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalHardreset:Sanitize

Fault Code: F78421

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78421

mibFaultName: fsmRmtErrComputePhysicalHardresetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSoftreset:Execute

Fault Code: F78422

Message

[FSM:STAGE:REMOTE-ERROR]: Soft-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78422

mibFaultName: fsmRmtErrComputePhysicalSoftresetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSoftreset:PreSanitize

Fault Code: F78422

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78422

mibFaultName: fsmRmtErrComputePhysicalSoftresetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSoftreset:Sanitize

Fault Code: F78422

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78422

mibFaultName: fsmRmtErrComputePhysicalSoftresetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSwConnUpd:A

Fault Code: F78423

Message

[FSM:STAGE:REMOTE-ERROR]: Updating fabric A for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:A)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: a-failed

mibFaultCode: 78423

mibFaultName: fsmRmtErrComputePhysicalSwConnUpdA

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalSwConnUpd:B

Fault Code: F78423

Message

[FSM:STAGE:REMOTE-ERROR]: Updating fabric B for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:B)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: b-failed

mibFaultCode: 78423

mibFaultName: fsmRmtErrComputePhysicalSwConnUpdB

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Cleanup

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Completing BIOS recovery mode for server [dn], and shutting it down(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Cleanup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryCleanup

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:PreSanitize

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Reset

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting server [dn] power state after BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Sanitize

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoverySanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:SetupVmediaLocal

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:SetupVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-local-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoverySetupVmediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:SetupVmediaPeer

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:SetupVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: setup-vmedia-peer-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoverySetupVmediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Shutdown

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Shutting down server [dn] to prepare for BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Start

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Running BIOS recovery on server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryStart

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:StopVMediaLocal

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:StopVMediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-local-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryStopVMediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:StopVMediaPeer

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:StopVMediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stopvmedia-peer-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryStopVMediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:TeardownVmediaLocal

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:TeardownVmediaLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-local-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryTeardownVmediaLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:TeardownVmediaPeer

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:TeardownVmediaPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: teardown-vmedia-peer-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryTeardownVmediaPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalBiosRecovery:Wait

Fault Code: F78424

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for completion of BIOS recovery for server [dn] (up to 15 min)(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Wait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-failed

mibFaultCode: 78424

mibFaultName: fsmRmtErrComputePhysicalBiosRecoveryWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:BladePowerOn

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:BladePowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-on-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetBladePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:Execute

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting CMOS for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:PreSanitize

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetPreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:ReconfigBios

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Reconfiguring BIOS Settings and Boot Order of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reconfig-bios-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetReconfigBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:ReconfigUuid

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Reconfiguring logical UUID of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigUuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reconfig-uuid-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetReconfigUuid

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalCmosReset:Sanitize

Fault Code: F78426

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78426

mibFaultName: fsmRmtErrComputePhysicalCmosResetSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalResetBmc:Execute

Fault Code: F78427

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting Management Controller on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetBmc:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78427

mibFaultName: fsmRmtErrComputePhysicalResetBmcExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrEquipmentIOCardResetIom:Execute

Fault Code: F78428

Message

[FSM:STAGE:REMOTE-ERROR]: Reset IOM [id] on Fex [chassisId](FSM-STAGE:sam:dme:EquipmentIOCardResetIom:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78428

mibFaultName: fsmRmtErrEquipmentIOCardResetIomExecute

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrComputeRackUnitDiscover:BiosPostCompletion

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBiosPostCompletion

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BladePowerOff

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: power on server [id] for discovery(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBladePowerOff

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcConfigPnuOS

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcConfigPnuOS

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcConfigureConnLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcConfigureConnLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcConfigureConnPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcConfigureConnPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcInventory

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: getting inventory of server [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-inventory-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcPreconfigPnuOSLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcPreconfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcPreconfigPnuOSPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcPreconfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcPresence

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: checking CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcPresence)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-presence-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcPresence

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcShutdownDiscovered

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown the server [id]; deep discovery completed(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcShutdownDiscovered)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-shutdown-discovered-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcShutdownDiscovered

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BmcUnconfigPnuOS

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the bootable device for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBmcUnconfigPnuOS

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BootPnuos

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: power server [id] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBootPnuos

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:BootWait

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverBootWait

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:ConfigDiscoveryMode

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: setting adapter mode to discovery for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigDiscoveryMode)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-discovery-mode-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverConfigDiscoveryMode

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:ConfigFlexFlashScrub

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring FlexFlash Scrub on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigFlexFlashScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-flex-flash-scrub-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverConfigFlexFlashScrub

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:ConfigNivMode

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: setting adapter mode to NIV for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigNivMode)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-niv-mode-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverConfigNivMode

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:ConfigUserAccess

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configuring external user access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigUserAccess)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-user-access-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverConfigUserAccess

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:HandlePooling

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Invoke post-discovery policies on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:HandlePooling)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: handle-pooling-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverHandlePooling

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:NicConfigPnuOSLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configure primary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverNicConfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:NicConfigPnuOSPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configure secondary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverNicConfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:NicInventoryLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicInventoryLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverNicInventoryLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:NicInventoryPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:NicInventoryPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-inventory-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverNicInventoryPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:OobStorageInventory

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: getting oob storage inventory of server [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:OobStorageInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: oob-storage-inventory-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverOobStorageInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSCatalog

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot catalog to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSCatalog

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSConnStatus

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconn-status-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSConnStatus

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSConnectivity

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnectivity)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconnectivity-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSConnectivity

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSIdent

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSIdent

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSInventory

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Perform inventory of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSInventory

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSPolicy

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot environment behavior policy to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSPolicy

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSScrub

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Scrub server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSScrub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosscrub-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSScrub

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PnuOSSelfTest

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger self-test of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPnuOSSelfTest

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:PreSanitize

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverPreSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:ReadSmbios

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for SMBIOS table from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ReadSmbios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: read-smbios-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverReadSmbios

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:Sanitize

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SolRedirectDisable

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol Redirection on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSolRedirectDisable

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SolRedirectEnable

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token on server [id] for Sol redirect(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSolRedirectEnable

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigPnuOSLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigPnuOSLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigPnuOSPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigPnuOSPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigPortNivLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configuring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigPortNivLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigPortNivPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: configuring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigPortNivPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigureConnLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigureConnLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwConfigureConnPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwConfigureConnPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwPnuOSConnectivityLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-pnuosconnectivity-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwPnuOSConnectivityLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwPnuOSConnectivityPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-pnuosconnectivity-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwPnuOSConnectivityPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwUnconfigPortNivLocal

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-port-niv-local-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwUnconfigPortNivLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:SwUnconfigPortNivPeer

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-port-niv-peer-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSwUnconfigPortNivPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:UnconfigCimcVMedia

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all bmc mappings for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverUnconfigCimcVMedia

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:UnconfigExtMgmtGw

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverUnconfigExtMgmtGw

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:UnconfigExtMgmtRules

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverUnconfigExtMgmtRules

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:hagConnect

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:hagConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-connect-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverHagConnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:hagDisconnect

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:hagDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-disconnect-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverHagDisconnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:serialDebugConnect

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:serialDebugConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-connect-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSerialDebugConnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:serialDebugDisconnect

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:serialDebugDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-disconnect-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverSerialDebugDisconnect

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitDiscover:waitForConnReady

Fault Code: F78434

Message

[FSM:STAGE:REMOTE-ERROR]: wait for connection to be established(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:waitForConnReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-conn-ready-failed

mibFaultCode: 78434

mibFaultName: fsmRmtErrComputeRackUnitDiscoverWaitForConnReady

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrLsServerConfigure:AnalyzeImpact

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Analyzing changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: analyze-impact-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureAnalyzeImpact

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ApplyConfig

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Applying config to server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureApplyConfig

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ApplyDefaultIdentifiers

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving and applying default identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyDefaultIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-default-identifiers-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureApplyDefaultIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ApplyIdentifiers

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving and applying identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-identifiers-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureApplyIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ApplyPolicies

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving and applying policies(FSM-STAGE:sam:dme:LsServerConfigure:ApplyPolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-policies-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureApplyPolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ApplyTemplate

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Applying configuration template [srcTemplName](FSM-STAGE:sam:dme:LsServerConfigure:ApplyTemplate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-template-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureApplyTemplate

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:CommitStorage

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: committing storage for service profile(FSM-STAGE:sam:dme:LsServerConfigure:CommitStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: commit-storage-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureCommitStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:EvaluateAssociation

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Evaluate association with server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:EvaluateAssociation)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-association-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureEvaluateAssociation

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ProvisionStorage

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving storage policy(FSM-STAGE:sam:dme:LsServerConfigure:ProvisionStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: provision-storage-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureProvisionStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveBootConfig

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Computing binding changes(FSM-STAGE:sam:dme:LsServerConfigure:ResolveBootConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-boot-config-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveBootConfig

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveDefaultIdentifiers

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving default identifiers from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDefaultIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-default-identifiers-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveDefaultIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveDistributable

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveDistributable

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveDistributableNames

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving distributable names from host pack(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveDistributableNames

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveIdentifiers

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving identifiers from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveIdentifiers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-identifiers-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveIdentifiers

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveImages

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveImages

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveNetworkPolicies

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving various dependent policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkPolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-network-policies-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveNetworkPolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveNetworkTemplates

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving various template policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkTemplates)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-network-templates-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveNetworkTemplates

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolvePolicies

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving various policies from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolvePolicies)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-policies-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolvePolicies

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ResolveSchedule

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving schedule policy from Firepower Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveSchedule)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-schedule-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureResolveSchedule

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:ValidatePolicyOwnership

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Validating policy integrity from ownership perspective(FSM-STAGE:sam:dme:LsServerConfigure:ValidatePolicyOwnership)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-policy-ownership-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureValidatePolicyOwnership

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:WaitForAssocCompletion

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Association completion on server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:WaitForAssocCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-assoc-completion-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureWaitForAssocCompletion

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:WaitForCommitStorage

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for storage commit to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForCommitStorage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-commit-storage-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureWaitForCommitStorage

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:WaitForMaintPermission

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for ack or maint window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintPermission)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-maint-permission-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureWaitForMaintPermission

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:WaitForMaintWindow

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for maintenance window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintWindow)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-maint-window-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureWaitForMaintWindow

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:WaitForStorageProvision

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for storage provisioning to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForStorageProvision)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-storage-provision-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureWaitForStorageProvision

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:checkAssignedDefaultIdentifiersForDup

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: checking assigned identifiers(from default pool) for dup(FSM-STAGE:sam:dme:LsServerConfigure:checkAssignedDefaultIdentifiersForDup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-assigned-default-identifiers-for-dup-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureCheckAssignedDefaultIdentifiersForDup

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrLsServerConfigure:checkAssignedIdentifiersForDup

Fault Code: F78435

Message

[FSM:STAGE:REMOTE-ERROR]: checking assigned identifiers for dup(FSM-STAGE:sam:dme:LsServerConfigure:checkAssignedIdentifiersForDup)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-assigned-identifiers-for-dup-failed

mibFaultCode: 78435

mibFaultName: fsmRmtErrLsServerConfigureCheckAssignedIdentifiersForDup

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmRmtErrSwEthMonDeploy:UpdateEthMon

Fault Code: F78440

Message

[FSM:STAGE:REMOTE-ERROR]: Ethernet traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwEthMonDeploy:UpdateEthMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-eth-mon-failed

mibFaultCode: 78440

mibFaultName: fsmRmtErrSwEthMonDeployUpdateEthMon

moClass: sw:EthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]

fsmRmtErrSwFcMonDeploy:UpdateFcMon

Fault Code: F78441

Message

[FSM:STAGE:REMOTE-ERROR]: FC traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwFcMonDeploy:UpdateFcMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-fc-mon-failed

mibFaultCode: 78441

mibFaultName: fsmRmtErrSwFcMonDeployUpdateFcMon

moClass: sw:FcMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]

fsmRmtErrFabricSanCloudSwitchMode:SwConfigLocal

Fault Code: F78442

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:FabricSanCloudSwitchMode:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 78442

mibFaultName: fsmRmtErrFabricSanCloudSwitchModeSwConfigLocal

moClass: fabric:SanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/san

fsmRmtErrFabricSanCloudSwitchMode:SwConfigPeer

Fault Code: F78442

Message

[FSM:STAGE:REMOTE-ERROR]: Fabric interconnect FC mode configuration to primary(FSM-STAGE:sam:dme:FabricSanCloudSwitchMode:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 78442

mibFaultName: fsmRmtErrFabricSanCloudSwitchModeSwConfigPeer

moClass: fabric:SanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/san

fsmRmtErrComputePhysicalUpdateExtUsers:Deploy

Fault Code: F78448

Message

[FSM:STAGE:REMOTE-ERROR]: external mgmt user deployment on server [dn] (profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalUpdateExtUsers:Deploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deploy-failed

mibFaultCode: 78448

mibFaultName: fsmRmtErrComputePhysicalUpdateExtUsersDeploy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrSysdebugTechSupportInitiate:Local

Fault Code: F78452

Message

[FSM:STAGE:REMOTE-ERROR]: create tech-support file from GUI on local(FSM-STAGE:sam:dme:SysdebugTechSupportInitiate:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78452

mibFaultName: fsmRmtErrSysdebugTechSupportInitiateLocal

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDeleteTechSupFile:Local

Fault Code: F78453

Message

[FSM:STAGE:REMOTE-ERROR]: delete tech-support file from GUI on local(FSM-STAGE:sam:dme:SysdebugTechSupportDeleteTechSupFile:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78453

mibFaultName: fsmRmtErrSysdebugTechSupportDeleteTechSupFileLocal

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDeleteTechSupFile:peer

Fault Code: F78453

Message

[FSM:STAGE:REMOTE-ERROR]: delete tech-support file from GUI on peer(FSM-STAGE:sam:dme:SysdebugTechSupportDeleteTechSupFile:peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78453

mibFaultName: fsmRmtErrSysdebugTechSupportDeleteTechSupFilePeer

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDownload:CopyPrimary

Fault Code: F78454

Message

[FSM:STAGE:REMOTE-ERROR]: Copy the tech-support file to primary for download(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:CopyPrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-primary-failed

mibFaultCode: 78454

mibFaultName: fsmRmtErrSysdebugTechSupportDownloadCopyPrimary

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDownload:CopySub

Fault Code: F78454

Message

[FSM:STAGE:REMOTE-ERROR]: copy tech-support file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:CopySub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-sub-failed

mibFaultCode: 78454

mibFaultName: fsmRmtErrSysdebugTechSupportDownloadCopySub

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDownload:DeletePrimary

Fault Code: F78454

Message

[FSM:STAGE:REMOTE-ERROR]: Delete the tech-support file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:DeletePrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-primary-failed

mibFaultCode: 78454

mibFaultName: fsmRmtErrSysdebugTechSupportDownloadDeletePrimary

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrSysdebugTechSupportDownload:DeleteSub

Fault Code: F78454

Message

[FSM:STAGE:REMOTE-ERROR]: Delete the tech-support file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugTechSupportDownload:DeleteSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-sub-failed

mibFaultCode: 78454

mibFaultName: fsmRmtErrSysdebugTechSupportDownloadDeleteSub

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmRmtErrComputePhysicalUpdateAdaptor:CheckPowerAvailability

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:PollUpdateStatusLocal

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-local-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorPollUpdateStatusLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:PollUpdateStatusPeer

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-peer-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorPollUpdateStatusPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:PowerDeployWait

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorPowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:PowerOff

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-off-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:PowerOn

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:UpdateRequestLocal

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-local-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorUpdateRequestLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateAdaptor:UpdateRequestPeer

Fault Code: F78483

Message

[FSM:STAGE:REMOTE-ERROR]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-peer-failed

mibFaultCode: 78483

mibFaultName: fsmRmtErrComputePhysicalUpdateAdaptorUpdateRequestPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:ActivateLocal

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-local-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorActivateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:ActivatePeer

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-peer-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorActivatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:CheckPowerAvailability

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:DeassertResetBypass

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:PowerDeployWait

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorPowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:PowerOn

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateAdaptor:Reset

Fault Code: F78484

Message

[FSM:STAGE:REMOTE-ERROR]: reseting the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 78484

mibFaultName: fsmRmtErrComputePhysicalActivateAdaptorReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrCapabilityCatalogueActivateCatalog:ApplyCatalog

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:ApplyCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-catalog-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogApplyCatalog

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:CopyCatFromRep

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: Copying Catalogue from repository to FI(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyCatFromRep)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-cat-from-rep-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogCopyCatFromRep

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:CopyExternalRepToRemote

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: syncing external repository to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyExternalRepToRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-external-rep-to-remote-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogCopyExternalRepToRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:CopyRemote

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: syncing catalog changes to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogCopyRemote

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:EvaluateStatus

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogEvaluateStatus

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:RescanImages

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: rescanning image files(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogRescanImages

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityCatalogueActivateCatalog:UnpackLocal

Fault Code: F78485

Message

[FSM:STAGE:REMOTE-ERROR]: activating catalog changes(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 78485

mibFaultName: fsmRmtErrCapabilityCatalogueActivateCatalogUnpackLocal

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmRmtErrCapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog

Fault Code: F78486

Message

[FSM:STAGE:REMOTE-ERROR]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-catalog-failed

mibFaultCode: 78486

mibFaultName: fsmRmtErrCapabilityMgmtExtensionActivateMgmtExtApplyCatalog

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmRmtErrCapabilityMgmtExtensionActivateMgmtExt:CopyRemote

Fault Code: F78486

Message

[FSM:STAGE:REMOTE-ERROR]: syncing management extension changes to subordinate(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78486

mibFaultName: fsmRmtErrCapabilityMgmtExtensionActivateMgmtExtCopyRemote

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmRmtErrCapabilityMgmtExtensionActivateMgmtExt:EvaluateStatus

Fault Code: F78486

Message

[FSM:STAGE:REMOTE-ERROR]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:EvaluateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: evaluate-status-failed

mibFaultCode: 78486

mibFaultName: fsmRmtErrCapabilityMgmtExtensionActivateMgmtExtEvaluateStatus

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmRmtErrCapabilityMgmtExtensionActivateMgmtExt:RescanImages

Fault Code: F78486

Message

[FSM:STAGE:REMOTE-ERROR]: rescanning image files(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:RescanImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: rescan-images-failed

mibFaultCode: 78486

mibFaultName: fsmRmtErrCapabilityMgmtExtensionActivateMgmtExtRescanImages

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmRmtErrCapabilityMgmtExtensionActivateMgmtExt:UnpackLocal

Fault Code: F78486

Message

[FSM:STAGE:REMOTE-ERROR]: activating management extension changes(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 78486

mibFaultName: fsmRmtErrCapabilityMgmtExtensionActivateMgmtExtUnpackLocal

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmRmtErrLicenseDownloaderDownload:CopyRemote

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: Copy the license file to subordinate for inventory(FSM-STAGE:sam:dme:LicenseDownloaderDownload:CopyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadCopyRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseDownloaderDownload:DeleteLocal

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: deleting temporary files for [fileName] on local(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-local-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadDeleteLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseDownloaderDownload:DeleteRemote

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: deleting temporary files for [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-remote-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadDeleteRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseDownloaderDownload:Local

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: downloading license file [fileName] from [server](FSM-STAGE:sam:dme:LicenseDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseDownloaderDownload:ValidateLocal

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: validation for license file [fileName] on primary(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-local-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadValidateLocal

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseDownloaderDownload:ValidateRemote

Fault Code: F78490

Message

[FSM:STAGE:REMOTE-ERROR]: validation for license file [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-remote-failed

mibFaultCode: 78490

mibFaultName: fsmRmtErrLicenseDownloaderDownloadValidateRemote

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmRmtErrLicenseFileInstall:Local

Fault Code: F78491

Message

[FSM:STAGE:REMOTE-ERROR]: Installing license on primary(FSM-STAGE:sam:dme:LicenseFileInstall:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78491

mibFaultName: fsmRmtErrLicenseFileInstallLocal

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmRmtErrLicenseFileInstall:Remote

Fault Code: F78491

Message

[FSM:STAGE:REMOTE-ERROR]: Installing license on subordinate(FSM-STAGE:sam:dme:LicenseFileInstall:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78491

mibFaultName: fsmRmtErrLicenseFileInstallRemote

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmRmtErrLicenseFileClear:Local

Fault Code: F78492

Message

[FSM:STAGE:REMOTE-ERROR]: Clearing license on primary(FSM-STAGE:sam:dme:LicenseFileClear:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78492

mibFaultName: fsmRmtErrLicenseFileClearLocal

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmRmtErrLicenseFileClear:Remote

Fault Code: F78492

Message

[FSM:STAGE:REMOTE-ERROR]: Clearing license on subordinate(FSM-STAGE:sam:dme:LicenseFileClear:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78492

mibFaultName: fsmRmtErrLicenseFileClearRemote

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmRmtErrLicenseInstanceUpdateFlexlm:Local

Fault Code: F78493

Message

[FSM:STAGE:REMOTE-ERROR]: Updating on primary(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78493

mibFaultName: fsmRmtErrLicenseInstanceUpdateFlexlmLocal

moClass: license:Instance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fsmRmtErrLicenseInstanceUpdateFlexlm:Remote

Fault Code: F78493

Message

[FSM:STAGE:REMOTE-ERROR]: Updating on subordinate(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm:Remote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remote-failed

mibFaultCode: 78493

mibFaultName: fsmRmtErrLicenseInstanceUpdateFlexlmRemote

moClass: license:Instance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fsmRmtErrComputePhysicalConfigSoL:Execute

Fault Code: F78523

Message

[FSM:STAGE:REMOTE-ERROR]: configuring SoL interface on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigSoL:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78523

mibFaultName: fsmRmtErrComputePhysicalConfigSoLExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUnconfigSoL:Execute

Fault Code: F78524

Message

[FSM:STAGE:REMOTE-ERROR]: removing SoL interface configuration from server [dn](FSM-STAGE:sam:dme:ComputePhysicalUnconfigSoL:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78524

mibFaultName: fsmRmtErrComputePhysicalUnconfigSoLExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrPortPIoInCompatSfpPresence:Shutdown

Fault Code: F78529

Message

[FSM:STAGE:REMOTE-ERROR]: Shutting down port(FSM-STAGE:sam:dme:PortPIoInCompatSfpPresence:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 78529

mibFaultName: fsmRmtErrPortPIoInCompatSfpPresenceShutdown

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmRmtErrComputePhysicalDiagnosticInterrupt:Execute

Fault Code: F78556

Message

[FSM:STAGE:REMOTE-ERROR]: Execute Diagnostic Interrupt(NMI) for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDiagnosticInterrupt:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78556

mibFaultName: fsmRmtErrComputePhysicalDiagnosticInterruptExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrSysdebugCoreDownload:CopyPrimary

Fault Code: F78573

Message

[FSM:STAGE:REMOTE-ERROR]: Copy the Core file to primary for download(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopyPrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-primary-failed

mibFaultCode: 78573

mibFaultName: fsmRmtErrSysdebugCoreDownloadCopyPrimary

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmRmtErrSysdebugCoreDownload:CopySub

Fault Code: F78573

Message

[FSM:STAGE:REMOTE-ERROR]: copy Core file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopySub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-sub-failed

mibFaultCode: 78573

mibFaultName: fsmRmtErrSysdebugCoreDownloadCopySub

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmRmtErrSysdebugCoreDownload:DeletePrimary

Fault Code: F78573

Message

[FSM:STAGE:REMOTE-ERROR]: Delete the Core file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeletePrimary)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-primary-failed

mibFaultCode: 78573

mibFaultName: fsmRmtErrSysdebugCoreDownloadDeletePrimary

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmRmtErrSysdebugCoreDownload:DeleteSub

Fault Code: F78573

Message

[FSM:STAGE:REMOTE-ERROR]: Delete the Core file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeleteSub)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-sub-failed

mibFaultCode: 78573

mibFaultName: fsmRmtErrSysdebugCoreDownloadDeleteSub

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmRmtErrEquipmentChassisDynamicReallocation:Config

Fault Code: F78574

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:EquipmentChassisDynamicReallocation:Config)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-failed

mibFaultCode: 78574

mibFaultName: fsmRmtErrEquipmentChassisDynamicReallocationConfig

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrComputePhysicalResetKvm:Execute

Fault Code: F78603

Message

[FSM:STAGE:REMOTE-ERROR]: Execute KVM Reset for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetKvm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78603

mibFaultName: fsmRmtErrComputePhysicalResetKvmExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrMgmtControllerOnline:BmcConfigureConnLocal

Fault Code: F78609

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-local-failed

mibFaultCode: 78609

mibFaultName: fsmRmtErrMgmtControllerOnlineBmcConfigureConnLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerOnline:BmcConfigureConnPeer

Fault Code: F78609

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-configure-conn-peer-failed

mibFaultCode: 78609

mibFaultName: fsmRmtErrMgmtControllerOnlineBmcConfigureConnPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerOnline:SwConfigureConnLocal

Fault Code: F78609

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-local-failed

mibFaultCode: 78609

mibFaultName: fsmRmtErrMgmtControllerOnlineSwConfigureConnLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerOnline:SwConfigureConnPeer

Fault Code: F78609

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-configure-conn-peer-failed

mibFaultCode: 78609

mibFaultName: fsmRmtErrMgmtControllerOnlineSwConfigureConnPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrComputeRackUnitOffline:CleanupLocal

Fault Code: F78610

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning host entries on local fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-local-failed

mibFaultCode: 78610

mibFaultName: fsmRmtErrComputeRackUnitOfflineCleanupLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitOffline:CleanupPeer

Fault Code: F78610

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning host entries on peer fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cleanup-peer-failed

mibFaultCode: 78610

mibFaultName: fsmRmtErrComputeRackUnitOfflineCleanupPeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitOffline:SwUnconfigureLocal

Fault Code: F78610

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigureLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfigure-local-failed

mibFaultCode: 78610

mibFaultName: fsmRmtErrComputeRackUnitOfflineSwUnconfigureLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitOffline:SwUnconfigurePeer

Fault Code: F78610

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigurePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfigure-peer-failed

mibFaultCode: 78610

mibFaultName: fsmRmtErrComputeRackUnitOfflineSwUnconfigurePeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrEquipmentLocatorLedSetFiLocatorLed:Execute

Fault Code: F78627

Message

[FSM:STAGE:REMOTE-ERROR]: setting FI locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFiLocatorLed:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78627

mibFaultName: fsmRmtErrEquipmentLocatorLedSetFiLocatorLedExecute

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmRmtErrFabricEpMgrConfigure:ApplyConfig

Fault Code: F78654

Message

[FSM:STAGE:REMOTE-ERROR]: Apply switch configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 78654

mibFaultName: fsmRmtErrFabricEpMgrConfigureApplyConfig

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmRmtErrFabricEpMgrConfigure:ApplyPhysical

Fault Code: F78654

Message

[FSM:STAGE:REMOTE-ERROR]: Applying physical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyPhysical)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-physical-failed

mibFaultCode: 78654

mibFaultName: fsmRmtErrFabricEpMgrConfigureApplyPhysical

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmRmtErrFabricEpMgrConfigure:ValidateConfiguration

Fault Code: F78654

Message

[FSM:STAGE:REMOTE-ERROR]: Validating logical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ValidateConfiguration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-configuration-failed

mibFaultCode: 78654

mibFaultName: fsmRmtErrFabricEpMgrConfigureValidateConfiguration

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmRmtErrFabricEpMgrConfigure:WaitOnPhys

Fault Code: F78654

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting on physical change application(FSM-STAGE:sam:dme:FabricEpMgrConfigure:WaitOnPhys)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-on-phys-failed

mibFaultCode: 78654

mibFaultName: fsmRmtErrFabricEpMgrConfigureWaitOnPhys

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmRmtErrVnicProfileSetDeployAlias:Local

Fault Code: F78663

Message

[FSM:STAGE:REMOTE-ERROR]: VNIC profile alias configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78663

mibFaultName: fsmRmtErrVnicProfileSetDeployAliasLocal

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmRmtErrVnicProfileSetDeployAlias:Peer

Fault Code: F78663

Message

[FSM:STAGE:REMOTE-ERROR]: VNIC profile alias configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78663

mibFaultName: fsmRmtErrVnicProfileSetDeployAliasPeer

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmRmtErrSwPhysConfPhysical:ConfigSwA

Fault Code: F78679

Message

[FSM:STAGE:REMOTE-ERROR]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-afailed

mibFaultCode: 78679

mibFaultName: fsmRmtErrSwPhysConfPhysicalConfigSwA

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmRmtErrSwPhysConfPhysical:ConfigSwB

Fault Code: F78679

Message

[FSM:STAGE:REMOTE-ERROR]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-bfailed

mibFaultCode: 78679

mibFaultName: fsmRmtErrSwPhysConfPhysicalConfigSwB

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmRmtErrSwPhysConfPhysical:PortInventorySwA

Fault Code: F78679

Message

[FSM:STAGE:REMOTE-ERROR]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-afailed

mibFaultCode: 78679

mibFaultName: fsmRmtErrSwPhysConfPhysicalPortInventorySwA

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmRmtErrSwPhysConfPhysical:PortInventorySwB

Fault Code: F78679

Message

[FSM:STAGE:REMOTE-ERROR]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-bfailed

mibFaultCode: 78679

mibFaultName: fsmRmtErrSwPhysConfPhysicalPortInventorySwB

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmRmtErrSwPhysConfPhysical:VerifyPhysConfig

Fault Code: F78679

Message

[FSM:STAGE:REMOTE-ERROR]: Verifying physical transition on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:VerifyPhysConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-phys-config-failed

mibFaultCode: 78679

mibFaultName: fsmRmtErrSwPhysConfPhysicalVerifyPhysConfig

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmRmtErrExtvmmEpClusterRole:SetLocal

Fault Code: F78694

Message

[FSM:STAGE:REMOTE-ERROR]: external VM management cluster role configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78694

mibFaultName: fsmRmtErrExtvmmEpClusterRoleSetLocal

moClass: extvmm:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt

fsmRmtErrExtvmmEpClusterRole:SetPeer

Fault Code: F78694

Message

[FSM:STAGE:REMOTE-ERROR]: external VM management cluster role configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78694

mibFaultName: fsmRmtErrExtvmmEpClusterRoleSetPeer

moClass: extvmm:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt

fsmRmtErrVmLifeCyclePolicyConfig:Local

Fault Code: F78699

Message

[FSM:STAGE:REMOTE-ERROR]: set Veth Auto-delete Retention Timer on local fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 78699

mibFaultName: fsmRmtErrVmLifeCyclePolicyConfigLocal

moClass: vm:LifeCyclePolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vm-lc-policy

fsmRmtErrVmLifeCyclePolicyConfig:Peer

Fault Code: F78699

Message

[FSM:STAGE:REMOTE-ERROR]: set Veth Auto-delete Retention Timer on peer fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 78699

mibFaultName: fsmRmtErrVmLifeCyclePolicyConfigPeer

moClass: vm:LifeCyclePolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vm-lc-policy

fsmRmtErrEquipmentBeaconLedIlluminate:ExecuteA

Fault Code: F78702

Message

[FSM:STAGE:REMOTE-ERROR]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-afailed

mibFaultCode: 78702

mibFaultName: fsmRmtErrEquipmentBeaconLedIlluminateExecuteA

moClass: equipment:BeaconLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/beacon

Affected MO: sys/chassis-[id]/blade-[slotId]/beacon

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/chassis-[id]/psu-[id]/beacon

Affected MO: sys/chassis-[id]/slot-[id]/beacon

Affected MO: sys/fex-[id]/beacon

Affected MO: sys/fex-[id]/psu-[id]/beacon

Affected MO: sys/fex-[id]/slot-[id]/beacon

Affected MO: sys/rack-unit-[id]/beacon

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/rack-unit-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/switch-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/slot-[id]/beacon

fsmRmtErrEquipmentBeaconLedIlluminate:ExecuteB

Fault Code: F78702

Message

[FSM:STAGE:REMOTE-ERROR]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-bfailed

mibFaultCode: 78702

mibFaultName: fsmRmtErrEquipmentBeaconLedIlluminateExecuteB

moClass: equipment:BeaconLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/beacon

Affected MO: sys/chassis-[id]/blade-[slotId]/beacon

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/chassis-[id]/psu-[id]/beacon

Affected MO: sys/chassis-[id]/slot-[id]/beacon

Affected MO: sys/fex-[id]/beacon

Affected MO: sys/fex-[id]/psu-[id]/beacon

Affected MO: sys/fex-[id]/slot-[id]/beacon

Affected MO: sys/rack-unit-[id]/beacon

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/rack-unit-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/switch-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/slot-[id]/beacon

fsmRmtErrEtherServerIntFIoConfigSpeed:Configure

Fault Code: F78711

Message

[FSM:STAGE:REMOTE-ERROR]: Configure admin speed for [dn](FSM-STAGE:sam:dme:EtherServerIntFIoConfigSpeed:Configure)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-failed

mibFaultCode: 78711

mibFaultName: fsmRmtErrEtherServerIntFIoConfigSpeedConfigure

moClass: ether:ServerIntFIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/rack-unit-[id]/diag/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmRmtErrComputePhysicalUpdateBIOS:Clear

Fault Code: F78721

Message

[FSM:STAGE:REMOTE-ERROR]: clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:Clear)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-failed

mibFaultCode: 78721

mibFaultName: fsmRmtErrComputePhysicalUpdateBIOSClear

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBIOS:PollClearStatus

Fault Code: F78721

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:PollClearStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-status-failed

mibFaultCode: 78721

mibFaultName: fsmRmtErrComputePhysicalUpdateBIOSPollClearStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBIOS:PollUpdateStatus

Fault Code: F78721

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 78721

mibFaultName: fsmRmtErrComputePhysicalUpdateBIOSPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBIOS:UpdateRequest

Fault Code: F78721

Message

[FSM:STAGE:REMOTE-ERROR]: sending BIOS update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 78721

mibFaultName: fsmRmtErrComputePhysicalUpdateBIOSUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:Activate

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: activating BIOS image(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSActivate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:Clear

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: clearing pending BIOS image activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Clear)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSClear

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:PollActivateStatus

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-status-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSPollActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:PollClearStatus

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image activate to clear(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollClearStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-status-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSPollClearStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:PowerOff

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-off-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:PowerOn

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: power on the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalActivateBIOS:UpdateTokens

Fault Code: F78722

Message

[FSM:STAGE:REMOTE-ERROR]: updating BIOS tokens(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:UpdateTokens)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-tokens-failed

mibFaultCode: 78722

mibFaultName: fsmRmtErrComputePhysicalActivateBIOSUpdateTokens

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrIdentIdentRequestUpdateIdent:Execute

Fault Code: F78752

Message

[FSM:STAGE:REMOTE-ERROR]: Update identities to external identifier manager(FSM-STAGE:sam:dme:IdentIdentRequestUpdateIdent:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78752

mibFaultName: fsmRmtErrIdentIdentRequestUpdateIdentExecute

moClass: ident:IdentRequest

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys/IdentQ-[id]

fsmRmtErrIdentMetaSystemSync:Execute

Fault Code: F78753

Message

[FSM:STAGE:REMOTE-ERROR]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78753

mibFaultName: fsmRmtErrIdentMetaSystemSyncExecute

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmRmtErrIdentMetaSystemSync:Ping

Fault Code: F78753

Message

[FSM:STAGE:REMOTE-ERROR]: Check identifier manager availability(FSM-STAGE:sam:dme:IdentMetaSystemSync:Ping)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: ping-failed

mibFaultCode: 78753

mibFaultName: fsmRmtErrIdentMetaSystemSyncPing

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmRmtErrComputePhysicalResetIpmi:Execute

Fault Code: F78766

Message

[FSM:STAGE:REMOTE-ERROR]: Execute Reset IPMI configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetIpmi:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78766

mibFaultName: fsmRmtErrComputePhysicalResetIpmiExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:ActivateBios

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:ActivateBios)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-bios-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeActivateBios

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BiosImgUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BiosImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-img-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBiosImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BiosPostCompletion

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BiosPostCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bios-post-completion-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBiosPostCompletion

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BladePowerOff

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Power off server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BladePowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: blade-power-off-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBladePowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BmcConfigPnuOS

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcConfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-config-pnuos-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBmcConfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BmcPreconfigPnuOSLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcPreconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuoslocal-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBmcPreconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BmcPreconfigPnuOSPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcPreconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-preconfig-pnuospeer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBmcPreconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BmcUnconfigPnuOS

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BmcUnconfigPnuOS)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: bmc-unconfig-pnuos-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBmcUnconfigPnuOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BootPnuos

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Bring-up pre-boot environment for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BootPnuos)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-pnuos-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBootPnuos

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:BootWait

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:BootWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: boot-wait-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeBootWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:CheckPowerAvailability

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Check if power can be allocated to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:CheckPowerAvailability)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-power-availability-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeCheckPowerAvailability

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:ClearBiosUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:ClearBiosUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clear-bios-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeClearBiosUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:DeassertResetBypass

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeDeassertResetBypass

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:DeleteCurlDownloadedImages

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Delete images downloaded from operations manager(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:DeleteCurlDownloadedImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-curl-downloaded-images-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeDeleteCurlDownloadedImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:GraphicsImageUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update gpu firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:GraphicsImageUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: graphics-image-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeGraphicsImageUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:HbaImgUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:HbaImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hba-img-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeHbaImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:LocalDiskFwUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:LocalDiskFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-disk-fw-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeLocalDiskFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:NicConfigPnuOSLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuoslocal-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeNicConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:NicConfigPnuOSPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-pnuospeer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeNicConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:NicImgUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-img-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeNicImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:NicUnconfigPnuOSLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuoslocal-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeNicUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:NicUnconfigPnuOSPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:NicUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-unconfig-pnuospeer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeNicUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSCatalog

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuoscatalog-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSCatalog

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSConfig

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosconfig-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSConfig

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSIdent

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSIdent)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosident-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSIdent

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSInventory

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosinventory-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSInventory

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSPolicy

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuospolicy-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSSelfTest

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSSelfTest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosself-test-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSSelfTest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSUnloadDrivers

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Unload drivers on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSUnloadDrivers)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosunload-drivers-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSUnloadDrivers

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PnuOSValidate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Pre-boot environment validation for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PnuOSValidate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pnuosvalidate-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePnuOSValidate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PollBiosActivateStatus

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBiosActivateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-activate-status-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePollBiosActivateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PollBiosUpdateStatus

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-bios-update-status-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePollBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PollBoardCtrlUpdateStatus

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollBoardCtrlUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-board-ctrl-update-status-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePollBoardCtrlUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PollClearBiosUpdateStatus

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PollClearBiosUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-clear-bios-update-status-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePollClearBiosUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PowerDeployWait

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for power allocation to server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PowerDeployWait)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-deploy-wait-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePowerDeployWait

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PowerOn

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-on-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:PreSanitize

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradePreSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:Sanitize

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSanitize

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:Shutdown

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Shutting down server [dn] after firmware upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Shutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SolRedirectDisable

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Disable Sol redirection on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SolRedirectDisable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-disable-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSolRedirectDisable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SolRedirectEnable

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: set up bios token for server for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SolRedirectEnable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sol-redirect-enable-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSolRedirectEnable

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:StorageCtlrImgUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:StorageCtlrImgUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: storage-ctlr-img-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeStorageCtlrImgUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwConfigPnuOSLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuoslocal-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwConfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwConfigPnuOSPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-pnuospeer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwConfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwConfigPortNivLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPortNivLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-local-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwConfigPortNivLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwConfigPortNivPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwConfigPortNivPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-port-niv-peer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwConfigPortNivPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwUnconfigPnuOSLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwUnconfigPnuOSLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuoslocal-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwUnconfigPnuOSLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:SwUnconfigPnuOSPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:SwUnconfigPnuOSPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-unconfig-pnuospeer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSwUnconfigPnuOSPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:UnconfigCimcVMedia

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all mappings for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigCimcVMedia)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-cimcvmedia-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUnconfigCimcVMedia

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:UnconfigExtMgmtGw

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt bmc gateway for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigExtMgmtGw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-gw-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUnconfigExtMgmtGw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:UnconfigExtMgmtRules

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: cleaning all ext mgmt rules for vmedia(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UnconfigExtMgmtRules)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfig-ext-mgmt-rules-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUnconfigExtMgmtRules

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:UpdateBiosRequest

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBiosRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bios-request-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUpdateBiosRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:UpdateBoardCtrlRequest

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBoardCtrlRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-board-ctrl-request-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUpdateBoardCtrlRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:activateAdaptorNwFwLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-local-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeActivateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:activateAdaptorNwFwPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-adaptor-nw-fw-peer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeActivateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:activateIBMCFw

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateibmcfw-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeActivateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:copyRemote

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Copy images to peer node(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:copyRemote)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: copy-remote-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeCopyRemote

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:downloadImages

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Download images from operations manager(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:downloadImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: download-images-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeDownloadImages

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:hagPnuOSConnect

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosconnect-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeHagPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:hagPnuOSDisconnect

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: hag-pnuosdisconnect-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeHagPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:resetIBMC

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:resetIBMC)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resetibmc-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeResetIBMC

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:serialDebugPnuOSConnect

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSConnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosconnect-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSerialDebugPnuOSConnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: serial-debug-pnuosdisconnect-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeSerialDebugPnuOSDisconnect

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:updateAdaptorNwFwLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-local-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUpdateAdaptorNwFwLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:updateAdaptorNwFwPeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-adaptor-nw-fw-peer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUpdateAdaptorNwFwPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:updateIBMCFw

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateIBMCFw)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateibmcfw-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeUpdateIBMCFw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-local-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeWaitForAdaptorNwFwUpdateLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-adaptor-nw-fw-update-peer-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeWaitForAdaptorNwFwUpdatePeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalFwUpgrade:waitForIBMCFwUpdate

Fault Code: F78767

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForIBMCFwUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-foribmcfw-update-failed

mibFaultCode: 78767

mibFaultName: fsmRmtErrComputePhysicalFwUpgradeWaitForIBMCFwUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitAdapterReset:DeassertResetBypass

Fault Code: F78768

Message

[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:DeassertResetBypass)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: deassert-reset-bypass-failed

mibFaultCode: 78768

mibFaultName: fsmRmtErrComputeRackUnitAdapterResetDeassertResetBypass

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitAdapterReset:PowerCycle

Fault Code: F78768

Message

[FSM:STAGE:REMOTE-ERROR]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PowerCycle)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-cycle-failed

mibFaultCode: 78768

mibFaultName: fsmRmtErrComputeRackUnitAdapterResetPowerCycle

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitAdapterReset:PreSanitize

Fault Code: F78768

Message

[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PreSanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pre-sanitize-failed

mibFaultCode: 78768

mibFaultName: fsmRmtErrComputeRackUnitAdapterResetPreSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitAdapterReset:Sanitize

Fault Code: F78768

Message

[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:Sanitize)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sanitize-failed

mibFaultCode: 78768

mibFaultName: fsmRmtErrComputeRackUnitAdapterResetSanitize

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrPortPIoInCompatSfpReplaced:EnablePort

Fault Code: F78798

Message

[FSM:STAGE:REMOTE-ERROR]: Enabling port(FSM-STAGE:sam:dme:PortPIoInCompatSfpReplaced:EnablePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-port-failed

mibFaultCode: 78798

mibFaultName: fsmRmtErrPortPIoInCompatSfpReplacedEnablePort

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmRmtErrExtpolEpRegisterFsm:Execute

Fault Code: F78799

Message

[FSM:STAGE:REMOTE-ERROR]: Register FSM Execute(FSM-STAGE:sam:dme:ExtpolEpRegisterFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78799

mibFaultName: fsmRmtErrExtpolEpRegisterFsmExecute

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrExtpolRegistryCrossDomainConfig:SetLocal

Fault Code: F78800

Message

[FSM:STAGE:REMOTE-ERROR]: Configure cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78800

mibFaultName: fsmRmtErrExtpolRegistryCrossDomainConfigSetLocal

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmRmtErrExtpolRegistryCrossDomainConfig:SetPeer

Fault Code: F78800

Message

[FSM:STAGE:REMOTE-ERROR]: Configure cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78800

mibFaultName: fsmRmtErrExtpolRegistryCrossDomainConfigSetPeer

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmRmtErrExtpolRegistryCrossDomainDelete:SetLocal

Fault Code: F78801

Message

[FSM:STAGE:REMOTE-ERROR]: Remove cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete:SetLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-local-failed

mibFaultCode: 78801

mibFaultName: fsmRmtErrExtpolRegistryCrossDomainDeleteSetLocal

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmRmtErrExtpolRegistryCrossDomainDelete:SetPeer

Fault Code: F78801

Message

[FSM:STAGE:REMOTE-ERROR]: Remove cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete:SetPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: set-peer-failed

mibFaultCode: 78801

mibFaultName: fsmRmtErrExtpolRegistryCrossDomainDeleteSetPeer

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmRmtErrNfsMountInstMount:MountLocal

Fault Code: F78817

Message

[FSM:STAGE:REMOTE-ERROR]: Mount nfs [remoteDir] from server [server] on local switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mount-local-failed

mibFaultCode: 78817

mibFaultName: fsmRmtErrNfsMountInstMountMountLocal

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountInstMount:MountPeer

Fault Code: F78817

Message

[FSM:STAGE:REMOTE-ERROR]: Mount nfs [remoteDir] from NFS server [server] on peer switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: mount-peer-failed

mibFaultCode: 78817

mibFaultName: fsmRmtErrNfsMountInstMountMountPeer

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountInstMount:RegisterClient

Fault Code: F78817

Message

[FSM:STAGE:REMOTE-ERROR]: Register client with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:RegisterClient)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: register-client-failed

mibFaultCode: 78817

mibFaultName: fsmRmtErrNfsMountInstMountRegisterClient

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountInstMount:VerifyRegistration

Fault Code: F78817

Message

[FSM:STAGE:REMOTE-ERROR]: Verify client registration with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:VerifyRegistration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-registration-failed

mibFaultCode: 78817

mibFaultName: fsmRmtErrNfsMountInstMountVerifyRegistration

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountInstUnmount:UnmountLocal

Fault Code: F78818

Message

[FSM:STAGE:REMOTE-ERROR]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unmount-local-failed

mibFaultCode: 78818

mibFaultName: fsmRmtErrNfsMountInstUnmountUnmountLocal

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountInstUnmount:UnmountPeer

Fault Code: F78818

Message

[FSM:STAGE:REMOTE-ERROR]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unmount-peer-failed

mibFaultCode: 78818

mibFaultName: fsmRmtErrNfsMountInstUnmountUnmountPeer

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmRmtErrNfsMountDefReportNfsMountSuspend:Report

Fault Code: F78819

Message

[FSM:STAGE:REMOTE-ERROR]: Report mount suspend success to operations manager(FSM-STAGE:sam:dme:NfsMountDefReportNfsMountSuspend:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 78819

mibFaultName: fsmRmtErrNfsMountDefReportNfsMountSuspendReport

moClass: nfs:MountDef

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: nfs-ep/nfs-mount-def-[name]

fsmRmtErrStorageSystemSync:Execute

Fault Code: F78835

Message

[FSM:STAGE:REMOTE-ERROR]: Synchronise requestors with storage broker(FSM-STAGE:sam:dme:StorageSystemSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78835

mibFaultName: fsmRmtErrStorageSystemSyncExecute

moClass: storage:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: storage-ep/system

fsmRmtErrFirmwareSystemDeploy:ActivateIOM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Activating IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateiom-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployActivateIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ActivateLocalFI

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Activating Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateLocalFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-localfi-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployActivateLocalFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ActivateMgmtExt

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Activating MgmtExt(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateMgmtExt)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-mgmt-ext-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployActivateMgmtExt

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ActivateRemoteFI

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Activating Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateRemoteFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-remotefi-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployActivateRemoteFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ActivateUCSM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Activating FPRM(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateUCSM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activateucsm-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployActivateUCSM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:DebundlePort

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Debundle the ports(FSM-STAGE:sam:dme:FirmwareSystemDeploy:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployDebundlePort

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollActivateOfIOM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-ofiom-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollActivateOfIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollActivateOfLocalFI

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfLocalFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-localfi-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollActivateOfLocalFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollActivateOfMgmtExt

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for MgmtExt Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfMgmtExt)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-mgmt-ext-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollActivateOfMgmtExt

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollActivateOfRemoteFI

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfRemoteFI)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-remotefi-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollActivateOfRemoteFI

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollActivateOfUCSM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for FPRM Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfUCSM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-ofucsm-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollActivateOfUCSM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollDebundlePort

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollDebundlePort

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:PollUpdateOfIOM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for update of IOMs to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollUpdateOfIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-ofiom-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployPollUpdateOfIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ResolveDistributable

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployResolveDistributable

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ResolveDistributableNames

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving distributable name from infra pack(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployResolveDistributableNames

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:ResolveImages

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployResolveImages

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:UpdateIOM

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Updating back-up image of IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:UpdateIOM)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: updateiom-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployUpdateIOM

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:WaitForDeploy

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Deploy to begin(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForDeploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-deploy-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployWaitForDeploy

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemDeploy:WaitForUserAck

Fault Code: F78848

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for User Acknowledgement To Start Primary Fabric Interconnect Activation(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForUserAck)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-user-ack-failed

mibFaultCode: 78848

mibFaultName: fsmRmtErrFirmwareSystemDeployWaitForUserAck

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemApplyCatalogPack:ActivateCatalog

Fault Code: F78849

Message

[FSM:STAGE:REMOTE-ERROR]: Activating Catalog(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ActivateCatalog)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-catalog-failed

mibFaultCode: 78849

mibFaultName: fsmRmtErrFirmwareSystemApplyCatalogPackActivateCatalog

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemApplyCatalogPack:ResolveDistributable

Fault Code: F78849

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributable)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-failed

mibFaultCode: 78849

mibFaultName: fsmRmtErrFirmwareSystemApplyCatalogPackResolveDistributable

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemApplyCatalogPack:ResolveDistributableNames

Fault Code: F78849

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving distributable name(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributableNames)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-distributable-names-failed

mibFaultCode: 78849

mibFaultName: fsmRmtErrFirmwareSystemApplyCatalogPackResolveDistributableNames

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrFirmwareSystemApplyCatalogPack:ResolveImages

Fault Code: F78849

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveImages)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-images-failed

mibFaultCode: 78849

mibFaultName: fsmRmtErrFirmwareSystemApplyCatalogPackResolveImages

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmRmtErrComputeServerDiscPolicyResolveScrubPolicy:Resolve

Fault Code: F78866

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving scrub policy from Firepower Central(FSM-STAGE:sam:dme:ComputeServerDiscPolicyResolveScrubPolicy:Resolve)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-failed

mibFaultCode: 78866

mibFaultName: fsmRmtErrComputeServerDiscPolicyResolveScrubPolicyResolve

moClass: compute:ServerDiscPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/server-discovery

fsmRmtErrSwFcSanBorderActivateZoneSet:UpdateZones

Fault Code: F78879

Message

[FSM:STAGE:REMOTE-ERROR]: fc zone configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderActivateZoneSet:UpdateZones)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-zones-failed

mibFaultCode: 78879

mibFaultName: fsmRmtErrSwFcSanBorderActivateZoneSetUpdateZones

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmRmtErrExtpolEpRepairCert:cleanOldData

Fault Code: F78886

Message

[FSM:STAGE:REMOTE-ERROR]: Cleaning certificates, channels and policy meta data(FSM-STAGE:sam:dme:ExtpolEpRepairCert:cleanOldData)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: clean-old-data-failed

mibFaultCode: 78886

mibFaultName: fsmRmtErrExtpolEpRepairCertCleanOldData

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrExtpolEpRepairCert:request

Fault Code: F78886

Message

[FSM:STAGE:REMOTE-ERROR]: Provisioning latest certificates(FSM-STAGE:sam:dme:ExtpolEpRepairCert:request)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-failed

mibFaultCode: 78886

mibFaultName: fsmRmtErrExtpolEpRepairCertRequest

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrExtpolEpRepairCert:unregister

Fault Code: F78886

Message

[FSM:STAGE:REMOTE-ERROR]: unregister from old FPR Central, if needed(FSM-STAGE:sam:dme:ExtpolEpRepairCert:unregister)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unregister-failed

mibFaultCode: 78886

mibFaultName: fsmRmtErrExtpolEpRepairCertUnregister

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrExtpolEpRepairCert:verify

Fault Code: F78886

Message

[FSM:STAGE:REMOTE-ERROR]: checking that cert was provisioned(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 78886

mibFaultName: fsmRmtErrExtpolEpRepairCertVerify

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrExtpolEpRepairCert:verifyGuid

Fault Code: F78886

Message

[FSM:STAGE:REMOTE-ERROR]: verifying GUID of FPR Central(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verifyGuid)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-guid-failed

mibFaultCode: 78886

mibFaultName: fsmRmtErrExtpolEpRepairCertVerifyGuid

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmRmtErrPolicyControlEpOperate:Resolve

Fault Code: F78887

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyControlEpOperate:Resolve)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-failed

mibFaultCode: 78887

mibFaultName: fsmRmtErrPolicyControlEpOperateResolve

moClass: policy:ControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]

fsmRmtErrPolicyPolicyScopeReleasePolicyFsm:Release

Fault Code: F78888

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleasePolicyFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 78888

mibFaultName: fsmRmtErrPolicyPolicyScopeReleasePolicyFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseOperationFsm:Release

Fault Code: F78889

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseOperationFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 78889

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseOperationFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseStorageFsm:Release

Fault Code: F78890

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseStorageFsm:Release)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-failed

mibFaultCode: 78890

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseStorageFsmRelease

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveManyPolicyFsm:ResolveMany

Fault Code: F78891

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyPolicyFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 78891

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveManyPolicyFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveManyOperationFsm:ResolveMany

Fault Code: F78892

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyOperationFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 78892

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveManyOperationFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveManyStorageFsm:ResolveMany

Fault Code: F78893

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyStorageFsm:ResolveMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-many-failed

mibFaultCode: 78893

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveManyStorageFsmResolveMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany

Fault Code: F78894

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 78894

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseManyPolicyFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany

Fault Code: F78895

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 78895

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseManyOperationFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany

Fault Code: F78896

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-many-failed

mibFaultCode: 78896

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseManyStorageFsmReleaseMany

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveAllPolicyFsm:ResolveAll

Fault Code: F78897

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllPolicyFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 78897

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveAllPolicyFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveAllOperationFsm:ResolveAll

Fault Code: F78898

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllOperationFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 78898

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveAllOperationFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeResolveAllStorageFsm:ResolveAll

Fault Code: F78899

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllStorageFsm:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 78899

mibFaultName: fsmRmtErrPolicyPolicyScopeResolveAllStorageFsmResolveAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll

Fault Code: F78900

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 78900

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseAllPolicyFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll

Fault Code: F78901

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 78901

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseAllOperationFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrPolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll

Fault Code: F78902

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-all-failed

mibFaultCode: 78902

mibFaultName: fsmRmtErrPolicyPolicyScopeReleaseAllStorageFsmReleaseAll

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmRmtErrMgmtExportPolicyReportConfigCopy:Report

Fault Code: F78924

Message

[FSM:STAGE:REMOTE-ERROR]: Report config copy to Ops Mgr(FSM-STAGE:sam:dme:MgmtExportPolicyReportConfigCopy:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 78924

mibFaultName: fsmRmtErrMgmtExportPolicyReportConfigCopyReport

moClass: mgmt:ExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/cfg-exp-policy-[name]

Affected MO: org-[name]/db-backup-policy-[name]

fsmRmtErrExtpolProviderReportConfigImport:Report

Fault Code: F78925

Message

[FSM:STAGE:REMOTE-ERROR]: Report config import to Ops Mgr(FSM-STAGE:sam:dme:ExtpolProviderReportConfigImport:Report)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-failed

mibFaultCode: 78925

mibFaultName: fsmRmtErrExtpolProviderReportConfigImportReport

moClass: extpol:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]

fsmRmtErrObserveObservedResolvePolicyFsm:Execute

Fault Code: F78931

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve Policy FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolvePolicyFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78931

mibFaultName: fsmRmtErrObserveObservedResolvePolicyFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmRmtErrObserveObservedResolveResourceFsm:Execute

Fault Code: F78932

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve Resource FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveResourceFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78932

mibFaultName: fsmRmtErrObserveObservedResolveResourceFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmRmtErrObserveObservedResolveVMFsm:Execute

Fault Code: F78933

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve VM FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveVMFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78933

mibFaultName: fsmRmtErrObserveObservedResolveVMFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmRmtErrObserveObservedResolveControllerFsm:Execute

Fault Code: F78934

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve Mgmt Controller FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveControllerFsm:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 78934

mibFaultName: fsmRmtErrObserveObservedResolveControllerFsmExecute

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmRmtErrMgmtControllerRegistryConfig:Remove

Fault Code: F78939

Message

[FSM:STAGE:REMOTE-ERROR]: Deleting registry information from config file(FSM-STAGE:sam:dme:MgmtControllerRegistryConfig:Remove)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: remove-failed

mibFaultCode: 78939

mibFaultName: fsmRmtErrMgmtControllerRegistryConfigRemove

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrGmetaHolderInventory:CheckInventoryStatus

Fault Code: F79048

Message

[FSM:STAGE:REMOTE-ERROR]: Throttle inventory(FSM-STAGE:sam:dme:GmetaHolderInventory:CheckInventoryStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-inventory-status-failed

mibFaultCode: 79048

mibFaultName: fsmRmtErrGmetaHolderInventoryCheckInventoryStatus

moClass: gmeta:Holder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: gmeta/category-[category]-provider-[provider]

fsmRmtErrGmetaHolderInventory:ReportFullInventory

Fault Code: F79048

Message

[FSM:STAGE:REMOTE-ERROR]: Report inventory to Firepower Central(FSM-STAGE:sam:dme:GmetaHolderInventory:ReportFullInventory)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: report-full-inventory-failed

mibFaultCode: 79048

mibFaultName: fsmRmtErrGmetaHolderInventoryReportFullInventory

moClass: gmeta:Holder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: gmeta/category-[category]-provider-[provider]

fsmRmtErrComputePhysicalCimcSessionDelete:Execute

Fault Code: F79049

Message

[FSM:STAGE:REMOTE-ERROR]: Terminating Cimc Sessions(FSM-STAGE:sam:dme:ComputePhysicalCimcSessionDelete:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 79049

mibFaultName: fsmRmtErrComputePhysicalCimcSessionDeleteExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrPolicyControlledTypeOperate:ResolveAll

Fault Code: F79052

Message

[FSM:STAGE:REMOTE-ERROR]: Resolving controlled type global policies(FSM-STAGE:sam:dme:PolicyControlledTypeOperate:ResolveAll)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-all-failed

mibFaultCode: 79052

mibFaultName: fsmRmtErrPolicyControlledTypeOperateResolveAll

moClass: policy:ControlledType

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]/cfg-backup-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/comm-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/datetime-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/discovery-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/dns-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fabric-fw-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fault-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/mep-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/monitoring-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/powermgmt-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/psu-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/security-ctrl/ctrlled-type-[type]

fsmRmtErrFabricVnetEpSyncEpPushVnetEpDeletion:Sync

Fault Code: F79059

Message

[FSM:STAGE:REMOTE-ERROR]: Update resource-mgr with VnetEp deletion(FSM-STAGE:sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion:Sync)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sync-failed

mibFaultCode: 79059

mibFaultName: fsmRmtErrFabricVnetEpSyncEpPushVnetEpDeletionSync

moClass: fabric:VnetEpSyncEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]/syncEp

fsmRmtErrSwEthLanFlowMonDeploy:UpdateEthFlowMon

Fault Code: F79079

Message

[FSM:STAGE:REMOTE-ERROR]: Ethernet traffic flow monitoring configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanFlowMonDeploy:UpdateEthFlowMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-eth-flow-mon-failed

mibFaultCode: 79079

mibFaultName: fsmRmtErrSwEthLanFlowMonDeployUpdateEthFlowMon

moClass: sw:EthLanFlowMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ethlanflowmon

fsmRmtErrMgmtIPv6IfAddrSwMgmtOobIpv6IfConfig:Switch

Fault Code: F79105

Message

[FSM:STAGE:REMOTE-ERROR]: configuring the out-of-band IPv6 interface(FSM-STAGE:sam:dme:MgmtIPv6IfAddrSwMgmtOobIpv6IfConfig:Switch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: switch-failed

mibFaultCode: 79105

mibFaultName: fsmRmtErrMgmtIPv6IfAddrSwMgmtOobIpv6IfConfigSwitch

moClass: mgmt:IPv6IfAddr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

fsmRmtErrComputePhysicalUpdateBoardController:PollUpdateStatus

Fault Code: F79107

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 79107

mibFaultName: fsmRmtErrComputePhysicalUpdateBoardControllerPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBoardController:PrepareForUpdate

Fault Code: F79107

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare for BoardController update(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:PrepareForUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: prepare-for-update-failed

mibFaultCode: 79107

mibFaultName: fsmRmtErrComputePhysicalUpdateBoardControllerPrepareForUpdate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBoardController:ServerPowerOff

Fault Code: F79107

Message

[FSM:STAGE:REMOTE-ERROR]: Power off server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:ServerPowerOff)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: server-power-off-failed

mibFaultCode: 79107

mibFaultName: fsmRmtErrComputePhysicalUpdateBoardControllerServerPowerOff

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBoardController:ServerPowerOn

Fault Code: F79107

Message

[FSM:STAGE:REMOTE-ERROR]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:ServerPowerOn)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: server-power-on-failed

mibFaultCode: 79107

mibFaultName: fsmRmtErrComputePhysicalUpdateBoardControllerServerPowerOn

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalUpdateBoardController:UpdateRequest

Fault Code: F79107

Message

[FSM:STAGE:REMOTE-ERROR]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBoardController:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 79107

mibFaultName: fsmRmtErrComputePhysicalUpdateBoardControllerUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrExtvmmNetworkSetsDeploy:Local

Fault Code: F79143

Message

[FSM:STAGE:REMOTE-ERROR]: VMNetworkDefinition configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmNetworkSetsDeploy:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 79143

mibFaultName: fsmRmtErrExtvmmNetworkSetsDeployLocal

moClass: extvmm:NetworkSets

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets

fsmRmtErrExtvmmNetworkSetsDeploy:Peer

Fault Code: F79143

Message

[FSM:STAGE:REMOTE-ERROR]: VMNetworkDefinition configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmNetworkSetsDeploy:Peer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 79143

mibFaultName: fsmRmtErrExtvmmNetworkSetsDeployPeer

moClass: extvmm:NetworkSets

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets

fsmRmtErrComputePhysicalConfigBoard:ConfigMemoryPolicy

Fault Code: F79147

Message

[FSM:STAGE:REMOTE-ERROR]: Configure Memory Configuration Policy on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigBoard:ConfigMemoryPolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-memory-policy-failed

mibFaultCode: 79147

mibFaultName: fsmRmtErrComputePhysicalConfigBoardConfigMemoryPolicy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalResetMemoryErrors:Execute

Fault Code: F79148

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting memory errors on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetMemoryErrors:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 79148

mibFaultName: fsmRmtErrComputePhysicalResetMemoryErrorsExecute

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrMgmtControllerExtMgmtInterfaceConfig:Active

Fault Code: F79154

Message

[FSM:STAGE:REMOTE-ERROR]: external in-band mgmt interface configuration on Active CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:Active)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: active-failed

mibFaultCode: 79154

mibFaultName: fsmRmtErrMgmtControllerExtMgmtInterfaceConfigActive

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgLocal

Fault Code: F79154

Message

[FSM:STAGE:REMOTE-ERROR]: in-band vlan configuration on Local CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cimcvlan-cfg-local-failed

mibFaultCode: 79154

mibFaultName: fsmRmtErrMgmtControllerExtMgmtInterfaceConfigCIMCVlanCfgLocal

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgPeer

Fault Code: F79154

Message

[FSM:STAGE:REMOTE-ERROR]: in-band vlan configuration on Peer CIMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CIMCVlanCfgPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cimcvlan-cfg-peer-failed

mibFaultCode: 79154

mibFaultName: fsmRmtErrMgmtControllerExtMgmtInterfaceConfigCIMCVlanCfgPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerExtMgmtInterfaceConfig:CMCVlanCfg

Fault Code: F79154

Message

[FSM:STAGE:REMOTE-ERROR]: in-band vlan configuration on CMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CMCVlanCfg)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cmcvlan-cfg-failed

mibFaultCode: 79154

mibFaultName: fsmRmtErrMgmtControllerExtMgmtInterfaceConfigCMCVlanCfg

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrMgmtControllerExtMgmtInterfaceConfig:CMCVlanCfgPeer

Fault Code: F79154

Message

[FSM:STAGE:REMOTE-ERROR]: in-band vlan configuration on CMC(FSM-STAGE:sam:dme:MgmtControllerExtMgmtInterfaceConfig:CMCVlanCfgPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: cmcvlan-cfg-peer-failed

mibFaultCode: 79154

mibFaultName: fsmRmtErrMgmtControllerExtMgmtInterfaceConfigCMCVlanCfgPeer

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrComputeRackUnitCreateDhcpEntry:ExecuteLocal

Fault Code: F79155

Message

[FSM:STAGE:REMOTE-ERROR]: Creating host entry in dhcp database(FSM-STAGE:sam:dme:ComputeRackUnitCreateDhcpEntry:ExecuteLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-local-failed

mibFaultCode: 79155

mibFaultName: fsmRmtErrComputeRackUnitCreateDhcpEntryExecuteLocal

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputeRackUnitCreateDhcpEntry:ExecutePeer

Fault Code: F79155

Message

[FSM:STAGE:REMOTE-ERROR]: Creating host entry in dhcp database(FSM-STAGE:sam:dme:ComputeRackUnitCreateDhcpEntry:ExecutePeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-peer-failed

mibFaultCode: 79155

mibFaultName: fsmRmtErrComputeRackUnitCreateDhcpEntryExecutePeer

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraDeploy:NicConfigLocal

Fault Code: F79156

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:NicConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-local-failed

mibFaultCode: 79156

mibFaultName: fsmRmtErrComputePhysicalServiceInfraDeployNicConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraDeploy:NicConfigPeer

Fault Code: F79156

Message

[FSM:STAGE:REMOTE-ERROR]: Configure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:NicConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-config-peer-failed

mibFaultCode: 79156

mibFaultName: fsmRmtErrComputePhysicalServiceInfraDeployNicConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraDeploy:SwConfigLocal

Fault Code: F79156

Message

[FSM:STAGE:REMOTE-ERROR]: Configure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:SwConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-local-failed

mibFaultCode: 79156

mibFaultName: fsmRmtErrComputePhysicalServiceInfraDeploySwConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraDeploy:SwConfigPeer

Fault Code: F79156

Message

[FSM:STAGE:REMOTE-ERROR]: Configure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraDeploy:SwConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-config-peer-failed

mibFaultCode: 79156

mibFaultName: fsmRmtErrComputePhysicalServiceInfraDeploySwConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraWithdraw:NicUnConfigLocal

Fault Code: F79157

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:NicUnConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-un-config-local-failed

mibFaultCode: 79157

mibFaultName: fsmRmtErrComputePhysicalServiceInfraWithdrawNicUnConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraWithdraw:NicUnConfigPeer

Fault Code: F79157

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter in server for service infrastructure ([assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:NicUnConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: nic-un-config-peer-failed

mibFaultCode: 79157

mibFaultName: fsmRmtErrComputePhysicalServiceInfraWithdrawNicUnConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraWithdraw:SwUnConfigLocal

Fault Code: F79157

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure service infrastructure on primary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:SwUnConfigLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-un-config-local-failed

mibFaultCode: 79157

mibFaultName: fsmRmtErrComputePhysicalServiceInfraWithdrawSwUnConfigLocal

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalServiceInfraWithdraw:SwUnConfigPeer

Fault Code: F79157

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure service infrastructure on secondary fabric Interconnect(FSM-STAGE:sam:dme:ComputePhysicalServiceInfraWithdraw:SwUnConfigPeer)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: sw-un-config-peer-failed

mibFaultCode: 79157

mibFaultName: fsmRmtErrComputePhysicalServiceInfraWithdrawSwUnConfigPeer

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrEquipmentIOCardBaseFePresence:CheckLicense

Fault Code: F79248

Message

[FSM:STAGE:REMOTE-ERROR]: Checking license for chassis [chassisId] (iom [id])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:CheckLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-license-failed

mibFaultCode: 79248

mibFaultName: fsmRmtErrEquipmentIOCardBaseFePresenceCheckLicense

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFePresence:ConfigChassisId

Fault Code: F79248

Message

[FSM:STAGE:REMOTE-ERROR]: identifying SwitchIOCard [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:ConfigChassisId)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-chassis-id-failed

mibFaultCode: 79248

mibFaultName: fsmRmtErrEquipmentIOCardBaseFePresenceConfigChassisId

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFePresence:Identify

Fault Code: F79248

Message

[FSM:STAGE:REMOTE-ERROR]: identifying IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardBaseFePresence:Identify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: identify-failed

mibFaultCode: 79248

mibFaultName: fsmRmtErrEquipmentIOCardBaseFePresenceIdentify

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:ConfigureEndPoint

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: configuring management identity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-end-point-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnConfigureEndPoint

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:ConfigureSwMgmtEndPoint

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: configuring fabric interconnect [switchId] mgmt connectivity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureSwMgmtEndPoint)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-sw-mgmt-end-point-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnConfigureSwMgmtEndPoint

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:ConfigureVifNs

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: configuring IOM [chassisId]/[id]([side]) virtual name space(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ConfigureVifNs)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-vif-ns-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnConfigureVifNs

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:DiscoverChassis

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: triggerring chassis discovery via IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:DiscoverChassis)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: discover-chassis-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnDiscoverChassis

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:EnableChassis

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: enabling chassis [chassisId] on [side] side(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:EnableChassis)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: enable-chassis-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnEnableChassis

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrEquipmentIOCardBaseFeConn:ResetBlades

Fault Code: F79249

Message

[FSM:STAGE:REMOTE-ERROR]: Reset Security Modules on [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardBaseFeConn:ResetBlades)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-blades-failed

mibFaultCode: 79249

mibFaultName: fsmRmtErrEquipmentIOCardBaseFeConnResetBlades

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmRmtErrMgmtControllerLockConfig:PowerButtonLockConfig

Fault Code: F79253

Message

[FSM:STAGE:REMOTE-ERROR]: Configuring Power Button Lock State(FSM-STAGE:sam:dme:MgmtControllerLockConfig:PowerButtonLockConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: power-button-lock-config-failed

mibFaultCode: 79253

mibFaultName: fsmRmtErrMgmtControllerLockConfigPowerButtonLockConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmRmtErrSdAppInstanceInstallApplication:Install

Fault Code: F79259

Message

[FSM:STAGE:REMOTE-ERROR]: Installing application(FSM-STAGE:sam:dme:SdAppInstanceInstallApplication:Install)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: install-failed

mibFaultCode: 79259

mibFaultName: fsmRmtErrSdAppInstanceInstallApplicationInstall

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceInstallApplication:UpdateAppInstance

Fault Code: F79259

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceInstallApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 79259

mibFaultName: fsmRmtErrSdAppInstanceInstallApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSysdebugLogExportPolicyConfigure:Local

Fault Code: F79270

Message

[FSM:STAGE:REMOTE-ERROR]: configuring log file export service on local(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Local)

Explanation

Cisco Firepower Manager could not set the configurations in the primary Fabric Interconnect for log file transfer to remote server.

Recommended Action

If you see this fault, take the following actions:

Step 1 Execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 79270

mibFaultName: fsmRmtErrSysdebugLogExportPolicyConfigureLocal

moClass: sysdebug:LogExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy

fsmRmtErrSysdebugLogExportPolicyConfigure:Peer

Fault Code: F79270

Message

[FSM:STAGE:REMOTE-ERROR]: configuring log file export service on peer(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Peer)

Explanation

Cisco Firepower Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for log file transfer to remote server. This fault typically appears for one of the following reasons:

- The subordinate FI is not reachable.

- The subordinate FI is experiencing an internal system error on applying the configuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the FI cluster state to ensure that the subordinate FI is reachable and functioning correctly. If the subordinate FI is down, take appropriate corrective actions so that the Firepower cluster goes into HA ready state.

Step 2 If the HA state of the primary and subordinate FIs are good, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: peer-failed

mibFaultCode: 79270

mibFaultName: fsmRmtErrSysdebugLogExportPolicyConfigurePeer

moClass: sysdebug:LogExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy

fsmRmtErrComputePhysicalFlashController:UpdateFlashLife

Fault Code: F79279

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Flash Life update to complete(FSM-STAGE:sam:dme:ComputePhysicalFlashController:UpdateFlashLife)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-flash-life-failed

mibFaultCode: 79279

mibFaultName: fsmRmtErrComputePhysicalFlashControllerUpdateFlashLife

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrOsControllerDeployOS:HostCheckImageValidationStatus

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Check for image validation status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckImageValidationStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-image-validation-status-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostCheckImageValidationStatus

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostCheckRommonReady

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Check for the Rommon first response status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckRommonReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-rommon-ready-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostCheckRommonReady

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostCheckUpgradeImageStatus

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Check for the image tftp status on blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerDeployOS:HostCheckUpgradeImageStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-check-upgrade-image-status-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostCheckUpgradeImageStatus

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostPrepareBoot

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare the boot command for [chassisId]/[slotId] and then boot the blade(FSM-STAGE:sam:dme:OsControllerDeployOS:HostPrepareBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-boot-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostPrepareBoot

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostPrepareKeyFile

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare Key file for ROMMON to boot(FSM-STAGE:sam:dme:OsControllerDeployOS:HostPrepareKeyFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-key-file-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostPrepareKeyFile

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostWaitForRommonReady

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for Rommon on blade [chassisId]/[slotId] to update the bootstatus.txt file(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForRommonReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-rommon-ready-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostWaitForRommonReady

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostWaitForRommonValidateImage

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for Rommon on blade [chassisId]/[slotId] to update the bootstatus.txt file(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForRommonValidateImage)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-rommon-validate-image-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostWaitForRommonValidateImage

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerDeployOS:HostWaitForSspOsRunning

Fault Code: F79303

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for OS on blade [chassisId]/[slotId] in service(FSM-STAGE:sam:dme:OsControllerDeployOS:HostWaitForSspOsRunning)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-ssp-os-running-failed

mibFaultCode: 79303

mibFaultName: fsmRmtErrOsControllerDeployOSHostWaitForSspOsRunning

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrNhTableHolderConfigureLinks:ApplyConfig

Fault Code: F79306

Message

[FSM:STAGE:REMOTE-ERROR]: Apply Configuration(FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 79306

mibFaultName: fsmRmtErrNhTableHolderConfigureLinksApplyConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmRmtErrNhTableHolderConfigureLinks:ConfigInterface

Fault Code: F79306

Message

[FSM:STAGE:REMOTE-ERROR]: Configure Interface(FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:ConfigInterface)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-interface-failed

mibFaultCode: 79306

mibFaultName: fsmRmtErrNhTableHolderConfigureLinksConfigInterface

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmRmtErrNhTableHolderConfigureLinks:VerifyLinkConfig

Fault Code: F79306

Message

[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:NhTableHolderConfigureLinks:VerifyLinkConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-link-config-failed

mibFaultCode: 79306

mibFaultName: fsmRmtErrNhTableHolderConfigureLinksVerifyLinkConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmRmtErrStorageFlexFlashControllerMOpsReset:Reset

Fault Code: F79312

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting FlexFlashController [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsReset:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 79312

mibFaultName: fsmRmtErrStorageFlexFlashControllerMOpsResetReset

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmRmtErrStorageFlexFlashControllerMOpsFormat:Format

Fault Code: F79313

Message

[FSM:STAGE:REMOTE-ERROR]: Formatting FlexFlash Cards in Controller [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsFormat:Format)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: format-failed

mibFaultCode: 79313

mibFaultName: fsmRmtErrStorageFlexFlashControllerMOpsFormatFormat

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmRmtErrStorageFlexFlashControllerMOpsPair:Pair

Fault Code: F79314

Message

[FSM:STAGE:REMOTE-ERROR]: Pair FlexFlash Cards in Controller [dn](FSM-STAGE:sam:dme:StorageFlexFlashControllerMOpsPair:Pair)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: pair-failed

mibFaultCode: 79314

mibFaultName: fsmRmtErrStorageFlexFlashControllerMOpsPairPair

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmRmtErrIdentMetaSystemUcscUnivSync:Execute

Fault Code: F79317

Message

[FSM:STAGE:REMOTE-ERROR]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemUcscUnivSync:Execute)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: execute-failed

mibFaultCode: 79317

mibFaultName: fsmRmtErrIdentMetaSystemUcscUnivSyncExecute

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmRmtErrComputePhysicalEnableCimcSecureBoot:Activate

Fault Code: F79337

Message

[FSM:STAGE:REMOTE-ERROR]: Activating CIMC image(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:Activate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-failed

mibFaultCode: 79337

mibFaultName: fsmRmtErrComputePhysicalEnableCimcSecureBootActivate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalEnableCimcSecureBoot:PollUpdateStatus

Fault Code: F79337

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:PollUpdateStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-update-status-failed

mibFaultCode: 79337

mibFaultName: fsmRmtErrComputePhysicalEnableCimcSecureBootPollUpdateStatus

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalEnableCimcSecureBoot:Reset

Fault Code: F79337

Message

[FSM:STAGE:REMOTE-ERROR]: Resetting CIMC to boot the activated version(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:Reset)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-failed

mibFaultCode: 79337

mibFaultName: fsmRmtErrComputePhysicalEnableCimcSecureBootReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrComputePhysicalEnableCimcSecureBoot:UpdateRequest

Fault Code: F79337

Message

[FSM:STAGE:REMOTE-ERROR]: Sending update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalEnableCimcSecureBoot:UpdateRequest)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-request-failed

mibFaultCode: 79337

mibFaultName: fsmRmtErrComputePhysicalEnableCimcSecureBootUpdateRequest

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmRmtErrSdAppInstanceStartApplication:DebundlePorts

Fault Code: F79351

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 79351

mibFaultName: fsmRmtErrSdAppInstanceStartApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStartApplication:Start

Fault Code: F79351

Message

[FSM:STAGE:REMOTE-ERROR]: Starting application(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:Start)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-failed

mibFaultCode: 79351

mibFaultName: fsmRmtErrSdAppInstanceStartApplicationStart

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStartApplication:UpdateAppInstance

Fault Code: F79351

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceStartApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 79351

mibFaultName: fsmRmtErrSdAppInstanceStartApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdLduProvisionLDU:CheckBladeReadiness

Fault Code: F79352

Message

[FSM:STAGE:REMOTE-ERROR]: Check if the blade is available to provision logical device.(FSM-STAGE:sam:dme:SdLduProvisionLDU:CheckBladeReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-blade-readiness-failed

mibFaultCode: 79352

mibFaultName: fsmRmtErrSdLduProvisionLDUCheckBladeReadiness

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmRmtErrSdLduProvisionLDU:StartApps

Fault Code: F79352

Message

[FSM:STAGE:REMOTE-ERROR]: Start the Apps(FSM-STAGE:sam:dme:SdLduProvisionLDU:StartApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-apps-failed

mibFaultCode: 79352

mibFaultName: fsmRmtErrSdLduProvisionLDUStartApps

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmRmtErrSdLduProvisionLDU:WaitForAppsInstallation

Fault Code: F79352

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for all the apps in the LDU to get installed.(FSM-STAGE:sam:dme:SdLduProvisionLDU:WaitForAppsInstallation)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-apps-installation-failed

mibFaultCode: 79352

mibFaultName: fsmRmtErrSdLduProvisionLDUWaitForAppsInstallation

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmRmtErrSdLduProvisionLDU:WaitForLinkConfiguration

Fault Code: F79352

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for CCL and MGMT Links configuration(FSM-STAGE:sam:dme:SdLduProvisionLDU:WaitForLinkConfiguration)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-link-configuration-failed

mibFaultCode: 79352

mibFaultName: fsmRmtErrSdLduProvisionLDUWaitForLinkConfiguration

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmRmtErrSwExtUtilityConfPortBreakout:ConfigSwA

Fault Code: F79357

Message

[FSM:STAGE:REMOTE-ERROR]: Configure port breakout mode mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:ConfigSwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-afailed

mibFaultCode: 79357

mibFaultName: fsmRmtErrSwExtUtilityConfPortBreakoutConfigSwA

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmRmtErrSwExtUtilityConfPortBreakout:ConfigSwB

Fault Code: F79357

Message

[FSM:STAGE:REMOTE-ERROR]: Configure port breakout mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:ConfigSwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: config-sw-bfailed

mibFaultCode: 79357

mibFaultName: fsmRmtErrSwExtUtilityConfPortBreakoutConfigSwB

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmRmtErrSwExtUtilityConfPortBreakout:PortInventorySwA

Fault Code: F79357

Message

[FSM:STAGE:REMOTE-ERROR]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:PortInventorySwA)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-afailed

mibFaultCode: 79357

mibFaultName: fsmRmtErrSwExtUtilityConfPortBreakoutPortInventorySwA

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmRmtErrSwExtUtilityConfPortBreakout:PortInventorySwB

Fault Code: F79357

Message

[FSM:STAGE:REMOTE-ERROR]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:PortInventorySwB)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: port-inventory-sw-bfailed

mibFaultCode: 79357

mibFaultName: fsmRmtErrSwExtUtilityConfPortBreakoutPortInventorySwB

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmRmtErrSwExtUtilityConfPortBreakout:VerifyBreakoutConfig

Fault Code: F79357

Message

[FSM:STAGE:REMOTE-ERROR]: Verifying physical port breakout config on fabric interconnect [id](FSM-STAGE:sam:dme:SwExtUtilityConfPortBreakout:VerifyBreakoutConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-breakout-config-failed

mibFaultCode: 79357

mibFaultName: fsmRmtErrSwExtUtilityConfPortBreakoutVerifyBreakoutConfig

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmRmtErrNhTableHolderBootstrapLinks:ApplyConfig

Fault Code: F79360

Message

[FSM:STAGE:REMOTE-ERROR]: Apply Configuration(FSM-STAGE:sam:dme:NhTableHolderBootstrapLinks:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 79360

mibFaultName: fsmRmtErrNhTableHolderBootstrapLinksApplyConfig

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmRmtErrLicenseSmartConfigSetConfig:Local

Fault Code: F79362

Message

[FSM:STAGE:REMOTE-ERROR]: Smart config change(FSM-STAGE:sam:dme:LicenseSmartConfigSetConfig:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 79362

mibFaultName: fsmRmtErrLicenseSmartConfigSetConfigLocal

moClass: license:SmartConfig

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/license-config-[operation]

fsmRmtErrApplicationDownloaderDownload:Local

Fault Code: F79368

Message

[FSM:STAGE:REMOTE-ERROR]: downloading image [fileName] from [server](FSM-STAGE:sam:dme:ApplicationDownloaderDownload:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 79368

mibFaultName: fsmRmtErrApplicationDownloaderDownloadLocal

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmRmtErrApplicationDownloaderDownload:UnpackLocal

Fault Code: F79368

Message

[FSM:STAGE:REMOTE-ERROR]: unpacking image [fileName] on primary(FSM-STAGE:sam:dme:ApplicationDownloaderDownload:UnpackLocal)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unpack-local-failed

mibFaultCode: 79368

mibFaultName: fsmRmtErrApplicationDownloaderDownloadUnpackLocal

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmRmtErrApplicationDownloaderDownload:Verify

Fault Code: F79368

Message

[FSM:STAGE:REMOTE-ERROR]: Image validation in progress(FSM-STAGE:sam:dme:ApplicationDownloaderDownload:Verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 79368

mibFaultName: fsmRmtErrApplicationDownloaderDownloadVerify

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmRmtErrSmAppDelete:Local

Fault Code: F79388

Message

[FSM:STAGE:REMOTE-ERROR]: deleting the Application [name].[version](FSM-STAGE:sam:dme:SmAppDelete:Local)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: local-failed

mibFaultCode: 79388

mibFaultName: fsmRmtErrSmAppDeleteLocal

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmRmtErrSmSecSvcRestoreApplication:Restore

Fault Code: F79389

Message

[FSM:STAGE:REMOTE-ERROR]: Restoring Apps in progress(FSM-STAGE:sam:dme:SmSecSvcRestoreApplication:Restore)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-failed

mibFaultCode: 79389

mibFaultName: fsmRmtErrSmSecSvcRestoreApplicationRestore

moClass: sm:SecSvc

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc

fsmRmtErrOsControllerUpgradeOS:HostWaitForUpgradeComplete

Fault Code: F79404

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for upgrade complete from blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:HostWaitForUpgradeComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-upgrade-complete-failed

mibFaultCode: 79404

mibFaultName: fsmRmtErrOsControllerUpgradeOSHostWaitForUpgradeComplete

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerUpgradeOS:RebootHostAfterUpgrade

Fault Code: F79404

Message

[FSM:STAGE:REMOTE-ERROR]: Reboot blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:RebootHostAfterUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reboot-host-after-upgrade-failed

mibFaultCode: 79404

mibFaultName: fsmRmtErrOsControllerUpgradeOSRebootHostAfterUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerUpgradeOS:RequestToUpgrade

Fault Code: F79404

Message

[FSM:STAGE:REMOTE-ERROR]: Request for upgrade to blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerUpgradeOS:RequestToUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-to-upgrade-failed

mibFaultCode: 79404

mibFaultName: fsmRmtErrOsControllerUpgradeOSRequestToUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerInitOS:HostPrepareBoot

Fault Code: F79405

Message

[FSM:STAGE:REMOTE-ERROR]: Prepare the boot command for blade [chassisId]/[slotId] to keep it in sync with MO(FSM-STAGE:sam:dme:OsControllerInitOS:HostPrepareBoot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-prepare-boot-failed

mibFaultCode: 79405

mibFaultName: fsmRmtErrOsControllerInitOSHostPrepareBoot

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerInitOS:HostWaitForUpgradeComplete

Fault Code: F79405

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for upgrade complete from blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:HostWaitForUpgradeComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: host-wait-for-upgrade-complete-failed

mibFaultCode: 79405

mibFaultName: fsmRmtErrOsControllerInitOSHostWaitForUpgradeComplete

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerInitOS:RebootHostAfterUpgrade

Fault Code: F79405

Message

[FSM:STAGE:REMOTE-ERROR]: Reboot blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:RebootHostAfterUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reboot-host-after-upgrade-failed

mibFaultCode: 79405

mibFaultName: fsmRmtErrOsControllerInitOSRebootHostAfterUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrOsControllerInitOS:RequestToUpgrade

Fault Code: F79405

Message

[FSM:STAGE:REMOTE-ERROR]: Request for upgrade to blade [chassisId]/[slotId](FSM-STAGE:sam:dme:OsControllerInitOS:RequestToUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: request-to-upgrade-failed

mibFaultCode: 79405

mibFaultName: fsmRmtErrOsControllerInitOSRequestToUpgrade

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmRmtErrSdAppInstanceUpgradeApplication:DebundlePorts

Fault Code: F79406

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 79406

mibFaultName: fsmRmtErrSdAppInstanceUpgradeApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceUpgradeApplication:UpdateAppInstance

Fault Code: F79406

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 79406

mibFaultName: fsmRmtErrSdAppInstanceUpgradeApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceUpgradeApplication:Upgrade

Fault Code: F79406

Message

[FSM:STAGE:REMOTE-ERROR]: Upgrading application(FSM-STAGE:sam:dme:SdAppInstanceUpgradeApplication:Upgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upgrade-failed

mibFaultCode: 79406

mibFaultName: fsmRmtErrSdAppInstanceUpgradeApplicationUpgrade

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStopApplication:DebundlePorts

Fault Code: F79407

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger (de)BundleDataPorts FSM(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:DebundlePorts)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-ports-failed

mibFaultCode: 79407

mibFaultName: fsmRmtErrSdAppInstanceStopApplicationDebundlePorts

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStopApplication:ReleaseAppLicense

Fault Code: F79407

Message

[FSM:STAGE:REMOTE-ERROR]: Release license of application instance(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:ReleaseAppLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-app-license-failed

mibFaultCode: 79407

mibFaultName: fsmRmtErrSdAppInstanceStopApplicationReleaseAppLicense

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStopApplication:Stop

Fault Code: F79407

Message

[FSM:STAGE:REMOTE-ERROR]: Stopping application(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:Stop)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-failed

mibFaultCode: 79407

mibFaultName: fsmRmtErrSdAppInstanceStopApplicationStop

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceStopApplication:UpdateAppInstance

Fault Code: F79407

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the operational state of application instance(FSM-STAGE:sam:dme:SdAppInstanceStopApplication:UpdateAppInstance)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-app-instance-failed

mibFaultCode: 79407

mibFaultName: fsmRmtErrSdAppInstanceStopApplicationUpdateAppInstance

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceUninstallApplication:ReleaseAppLicense

Fault Code: F79408

Message

[FSM:STAGE:REMOTE-ERROR]: Release license of application instance(FSM-STAGE:sam:dme:SdAppInstanceUninstallApplication:ReleaseAppLicense)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: release-app-license-failed

mibFaultCode: 79408

mibFaultName: fsmRmtErrSdAppInstanceUninstallApplicationReleaseAppLicense

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdAppInstanceUninstallApplication:Uninstall

Fault Code: F79408

Message

[FSM:STAGE:REMOTE-ERROR]: Uninstalling application(FSM-STAGE:sam:dme:SdAppInstanceUninstallApplication:Uninstall)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: uninstall-failed

mibFaultCode: 79408

mibFaultName: fsmRmtErrSdAppInstanceUninstallApplicationUninstall

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmRmtErrSdSlotChangePlatformLogLevel:SendCommand

Fault Code: F79409

Message

[FSM:STAGE:REMOTE-ERROR]: Send command to change the log level(FSM-STAGE:sam:dme:SdSlotChangePlatformLogLevel:SendCommand)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-command-failed

mibFaultCode: 79409

mibFaultName: fsmRmtErrSdSlotChangePlatformLogLevelSendCommand

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdLogicalDeviceConfigureLinks:ConfigureSwitch

Fault Code: F79411

Message

[FSM:STAGE:REMOTE-ERROR]: Invoke Port API to configure the switch(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:ConfigureSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-switch-failed

mibFaultCode: 79411

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureLinksConfigureSwitch

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdLogicalDeviceConfigureLinks:SendInterfaces

Fault Code: F79411

Message

[FSM:STAGE:REMOTE-ERROR]: Send Updated Interface Mapping(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:SendInterfaces)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-interfaces-failed

mibFaultCode: 79411

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureLinksSendInterfaces

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdLogicalDeviceConfigureLinks:UnconfigureLinks

Fault Code: F79411

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure Links in the LogicalDevice(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:UnconfigureLinks)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfigure-links-failed

mibFaultCode: 79411

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureLinksUnconfigureLinks

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdLogicalDeviceConfigureLinks:UnconfigureLogicalDevice

Fault Code: F79411

Message

[FSM:STAGE:REMOTE-ERROR]: Unconfigure logical device(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:UnconfigureLogicalDevice)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: unconfigure-logical-device-failed

mibFaultCode: 79411

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureLinksUnconfigureLogicalDevice

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdLogicalDeviceConfigureLinks:WaitForSwitchConfig

Fault Code: F79411

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for Switch configuration to complete(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureLinks:WaitForSwitchConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-config-failed

mibFaultCode: 79411

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureLinksWaitForSwitchConfig

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdSlotFormatDisk:CheckBladeReadiness

Fault Code: F79414

Message

[FSM:STAGE:REMOTE-ERROR]: Check blade readiness(FSM-STAGE:sam:dme:SdSlotFormatDisk:CheckBladeReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-blade-readiness-failed

mibFaultCode: 79414

mibFaultName: fsmRmtErrSdSlotFormatDiskCheckBladeReadiness

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdSlotFormatDisk:ResetBladePower

Fault Code: F79414

Message

[FSM:STAGE:REMOTE-ERROR]: Blade power reset(FSM-STAGE:sam:dme:SdSlotFormatDisk:ResetBladePower)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: reset-blade-power-failed

mibFaultCode: 79414

mibFaultName: fsmRmtErrSdSlotFormatDiskResetBladePower

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdSlotFormatDisk:StartDiskFormat

Fault Code: F79414

Message

[FSM:STAGE:REMOTE-ERROR]: Start formatting disk(FSM-STAGE:sam:dme:SdSlotFormatDisk:StartDiskFormat)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-disk-format-failed

mibFaultCode: 79414

mibFaultName: fsmRmtErrSdSlotFormatDiskStartDiskFormat

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdSlotFormatDisk:WaitForDiskFormatComplete

Fault Code: F79414

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for disk format complete(FSM-STAGE:sam:dme:SdSlotFormatDisk:WaitForDiskFormatComplete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-disk-format-complete-failed

mibFaultCode: 79414

mibFaultName: fsmRmtErrSdSlotFormatDiskWaitForDiskFormatComplete

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdSlotSynchTimeZone:UpdateTimeZone

Fault Code: F79415

Message

[FSM:STAGE:REMOTE-ERROR]: Update time zone(FSM-STAGE:sam:dme:SdSlotSynchTimeZone:UpdateTimeZone)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-time-zone-failed

mibFaultCode: 79415

mibFaultName: fsmRmtErrSdSlotSynchTimeZoneUpdateTimeZone

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmRmtErrSdAppAttributeCtrlGetAppAttributes:GetAttributes

Fault Code: F79416

Message

[FSM:STAGE:REMOTE-ERROR]: Retrive application attributes(FSM-STAGE:sam:dme:SdAppAttributeCtrlGetAppAttributes:GetAttributes)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: get-attributes-failed

mibFaultCode: 79416

mibFaultName: fsmRmtErrSdAppAttributeCtrlGetAppAttributesGetAttributes

moClass: sd:AppAttributeCtrl

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-attribute-ctrl

fsmRmtErrSdMgmtInfoUpdateMgmtInfo:SendUpdate

Fault Code: F79417

Message

[FSM:STAGE:REMOTE-ERROR]: Update management information(FSM-STAGE:sam:dme:SdMgmtInfoUpdateMgmtInfo:SendUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-update-failed

mibFaultCode: 79417

mibFaultName: fsmRmtErrSdMgmtInfoUpdateMgmtInfoSendUpdate

moClass: sd:MgmtInfo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/mgmt-info

fsmRmtErrSdNetMgmtBootstrapUpdateNetMgmtBootstrap:SendUpdate

Fault Code: F79418

Message

[FSM:STAGE:REMOTE-ERROR]: Send message to AppAgent(FSM-STAGE:sam:dme:SdNetMgmtBootstrapUpdateNetMgmtBootstrap:SendUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-update-failed

mibFaultCode: 79418

mibFaultName: fsmRmtErrSdNetMgmtBootstrapUpdateNetMgmtBootstrapSendUpdate

moClass: sd:NetMgmtBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/net-mgmt-bootstrap

fsmRmtErrFirmwarePlatformPackPlatformVersion:Restore

Fault Code: F79424

Message

[FSM:STAGE:REMOTE-ERROR]: Check and Restore the Platform Version(FSM-STAGE:sam:dme:FirmwarePlatformPackPlatformVersion:Restore)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: restore-failed

mibFaultCode: 79424

mibFaultName: fsmRmtErrFirmwarePlatformPackPlatformVersionRestore

moClass: firmware:PlatformPack

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fsmRmtErrFirmwarePlatformPackPlatformVersion:WaitForReady

Fault Code: F79424

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for system to be ready(FSM-STAGE:sam:dme:FirmwarePlatformPackPlatformVersion:WaitForReady)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-ready-failed

mibFaultCode: 79424

mibFaultName: fsmRmtErrFirmwarePlatformPackPlatformVersionWaitForReady

moClass: firmware:PlatformPack

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fsmRmtErrSwSspEthMonDeploy:UpdateSspEthMon

Fault Code: F79440

Message

[FSM:STAGE:REMOTE-ERROR]: SSP Packet Capture configuration on [switchId](FSM-STAGE:sam:dme:SwSspEthMonDeploy:UpdateSspEthMon)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-ssp-eth-mon-failed

mibFaultCode: 79440

mibFaultName: fsmRmtErrSwSspEthMonDeployUpdateSspEthMon

moClass: sw:SspEthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]

fsmRmtErrSdClusterBootstrapUpdateClusterConfiguration:SendConfig

Fault Code: F79443

Message

[FSM:STAGE:REMOTE-ERROR]: Send Updated Cluster Configuration(FSM-STAGE:sam:dme:SdClusterBootstrapUpdateClusterConfiguration:SendConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-config-failed

mibFaultCode: 79443

mibFaultName: fsmRmtErrSdClusterBootstrapUpdateClusterConfigurationSendConfig

moClass: sd:ClusterBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/cluster-bootstrap

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/cluster-bootstrap

fsmRmtErrSmAppUpdateApplication:Update

Fault Code: F79446

Message

[FSM:STAGE:REMOTE-ERROR]: Updating Apps in progress(FSM-STAGE:sam:dme:SmAppUpdateApplication:Update)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-failed

mibFaultCode: 79446

mibFaultName: fsmRmtErrSmAppUpdateApplicationUpdate

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmRmtErrSmAppInstanceResetApplication:CheckMainAppInstClusterStatus

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Check main app instance cluster status.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:CheckMainAppInstClusterStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-main-app-inst-cluster-status-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationCheckMainAppInstClusterStatus

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:StartApps

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Start main and decorator applications(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StartApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-apps-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationStartApps

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:StopDecoratorApps

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Stop decorator applications(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StopDecoratorApps)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-decorator-apps-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationStopDecoratorApps

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:StopMainApp

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Stop main application(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:StopMainApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-main-app-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationStopMainApp

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:WairForStopDecorators

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for stopping decorator applications to complete(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WairForStopDecorators)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wair-for-stop-decorators-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationWairForStopDecorators

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:WaitForBladeReboot

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for blade reboot(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForBladeReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-reboot-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationWaitForBladeReboot

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:WaitForMainAppInstInCluster

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for main app instance joins cluster.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForMainAppInstInCluster)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-main-app-inst-in-cluster-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationWaitForMainAppInstInCluster

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrSmAppInstanceResetApplication:WaitForStopMainApp

Fault Code: F79447

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for stopping main application to complete.(FSM-STAGE:sam:dme:SmAppInstanceResetApplication:WaitForStopMainApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-stop-main-app-failed

mibFaultCode: 79447

mibFaultName: fsmRmtErrSmAppInstanceResetApplicationWaitForStopMainApp

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmRmtErrIpsecEpUpdateEp:ApplyConfig

Fault Code: F79460

Message

[FSM:STAGE:REMOTE-ERROR]: configure IPsec connections(FSM-STAGE:sam:dme:IpsecEpUpdateEp:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 79460

mibFaultName: fsmRmtErrIpsecEpUpdateEpApplyConfig

moClass: ipsec:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext

fsmRmtErrEtherFtwPortPairConfigFtw:Configure

Fault Code: F79463

Message

[FSM:STAGE:REMOTE-ERROR]: Configure fail-to-wire for [dn](FSM-STAGE:sam:dme:EtherFtwPortPairConfigFtw:Configure)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-failed

mibFaultCode: 79463

mibFaultName: fsmRmtErrEtherFtwPortPairConfigFtwConfigure

moClass: ether:FtwPortPair

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/fail-to-wire/ftw-port-[slotId]-[aggrPortId]-[portId]-port-[peerSlotId]-[peerAggrPortId]-[peerPortId]

fsmRmtErrSdLinkUpdateInterfaceStatus:SendStatus

Fault Code: F79464

Message

[FSM:STAGE:REMOTE-ERROR]: Send Interface Operational State(FSM-STAGE:sam:dme:SdLinkUpdateInterfaceStatus:SendStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-status-failed

mibFaultCode: 79464

mibFaultName: fsmRmtErrSdLinkUpdateInterfaceStatusSendStatus

moClass: sd:Link

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:StartApp

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger FSM to start application(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:StartApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: start-app-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppStartApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:StopApp

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Stop application before upgrade(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:StopApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: stop-app-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppStopApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:UpgradeApp

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger FSM to upgrade application(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:UpgradeApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: upgrade-app-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppUpgradeApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:WaitForBladeReboot

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for blade reboot(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForBladeReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-reboot-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppWaitForBladeReboot

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:WaitForStopApp

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for application stop to complete.(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForStopApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-stop-app-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppWaitForStopApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSdUpgradeTaskStopUpgradeStartApp:WaitForUpgradeApp

Fault Code: F79465

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for application upgrade to complete.(FSM-STAGE:sam:dme:SdUpgradeTaskStopUpgradeStartApp:WaitForUpgradeApp)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-upgrade-app-failed

mibFaultCode: 79465

mibFaultName: fsmRmtErrSdUpgradeTaskStopUpgradeStartAppWaitForUpgradeApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmRmtErrSwSspEthMonSrcPhyEpDelete:DeletePcapFile

Fault Code: F79474

Message

[FSM:STAGE:REMOTE-ERROR]: Delete Pcap file whenever there is a delete interface trigger(FSM-STAGE:sam:dme:SwSspEthMonSrcPhyEpDelete:DeletePcapFile)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: delete-pcap-file-failed

mibFaultCode: 79474

mibFaultName: fsmRmtErrSwSspEthMonSrcPhyEpDeleteDeletePcapFile

moClass: sw:SspEthMonSrcPhyEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/ssp-mon-src-phy-[chassisId]-slot-[slotId]-port-[portId]-aggr-[aggrPortId]

fsmRmtErrFirmwareSupFirmwareDeploy:ActivateFirmwarePack

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Activating SUP Firmware(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:ActivateFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: activate-firmware-pack-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployActivateFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:CheckUpgradeStatus

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Check Upgrade Status(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:CheckUpgradeStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-upgrade-status-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployCheckUpgradeStatus

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:CompleteFirmwareUpgrade

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Complete Firmware Pack Upgrade(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:CompleteFirmwareUpgrade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: complete-firmware-upgrade-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployCompleteFirmwareUpgrade

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:DebundlePort

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Debundle the ports(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployDebundlePort

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:PollActivateOfFirmwarePack

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for FPRM Activate to complete(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:PollActivateOfFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-activate-of-firmware-pack-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployPollActivateOfFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:PollDebundlePort

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployPollDebundlePort

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:UpdateImageVersion

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Updating Image Version(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:UpdateImageVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-image-version-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployUpdateImageVersion

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:UpdatePackageVersion

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Updating Package Version(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:UpdatePackageVersion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-package-version-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployUpdatePackageVersion

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:ValidateFirmwarePack

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Validate the firmware pack(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:ValidateFirmwarePack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validate-firmware-pack-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployValidateFirmwarePack

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:WaitForDeploy

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Deploy to begin(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:WaitForDeploy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-deploy-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployWaitForDeploy

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrFirmwareSupFirmwareDeploy:WaitForFirmwareVersionUpdate

Fault Code: F79475

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Firmware Version to update(FSM-STAGE:sam:dme:FirmwareSupFirmwareDeploy:WaitForFirmwareVersionUpdate)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-firmware-version-update-failed

mibFaultCode: 79475

mibFaultName: fsmRmtErrFirmwareSupFirmwareDeployWaitForFirmwareVersionUpdate

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmRmtErrEquipmentChassisShutdownChassis:ApplyShutdown

Fault Code: F79483

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown Chassis(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:ApplyShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-shutdown-failed

mibFaultCode: 79483

mibFaultName: fsmRmtErrEquipmentChassisShutdownChassisApplyShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisShutdownChassis:DebundlePort

Fault Code: F79483

Message

[FSM:STAGE:REMOTE-ERROR]: Debundle the ports(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 79483

mibFaultName: fsmRmtErrEquipmentChassisShutdownChassisDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisShutdownChassis:PollDebundlePort

Fault Code: F79483

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 79483

mibFaultName: fsmRmtErrEquipmentChassisShutdownChassisPollDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisShutdownChassis:ShutdownBlade

Fault Code: F79483

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown Blade(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:ShutdownBlade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-blade-failed

mibFaultCode: 79483

mibFaultName: fsmRmtErrEquipmentChassisShutdownChassisShutdownBlade

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisShutdownChassis:WaitForBladeShutdown

Fault Code: F79483

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for blade shutdown(FSM-STAGE:sam:dme:EquipmentChassisShutdownChassis:WaitForBladeShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-shutdown-failed

mibFaultCode: 79483

mibFaultName: fsmRmtErrEquipmentChassisShutdownChassisWaitForBladeShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrSmCloudConnectorRegisterCloudConnector:Register

Fault Code: F79491

Message

[FSM:STAGE:REMOTE-ERROR]: Registering the device with cloud.(FSM-STAGE:sam:dme:SmCloudConnectorRegisterCloudConnector:Register)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: register-failed

mibFaultCode: 79491

mibFaultName: fsmRmtErrSmCloudConnectorRegisterCloudConnectorRegister

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmRmtErrSmCloudConnectorUnRegisterCloudConnector:UnRegister

Fault Code: F79492

Message

[FSM:STAGE:REMOTE-ERROR]: UnRegistering the device with cloud.(FSM-STAGE:sam:dme:SmCloudConnectorUnRegisterCloudConnector:UnRegister)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: un-register-failed

mibFaultCode: 79492

mibFaultName: fsmRmtErrSmCloudConnectorUnRegisterCloudConnectorUnRegister

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmRmtErrSmAppVerifyApplication:CheckReadiness

Fault Code: F79493

Message

[FSM:STAGE:REMOTE-ERROR]: Image validation queued(FSM-STAGE:sam:dme:SmAppVerifyApplication:CheckReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-readiness-failed

mibFaultCode: 79493

mibFaultName: fsmRmtErrSmAppVerifyApplicationCheckReadiness

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmRmtErrSmAppVerifyApplication:Verify

Fault Code: F79493

Message

[FSM:STAGE:REMOTE-ERROR]: Image validation in progress(FSM-STAGE:sam:dme:SmAppVerifyApplication:Verify)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: verify-failed

mibFaultCode: 79493

mibFaultName: fsmRmtErrSmAppVerifyApplicationVerify

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmRmtErrSmLogicalDeviceConfigure:ApplyConfig

Fault Code: F79496

Message

[FSM:STAGE:REMOTE-ERROR]: Apply configuration to physical end-points.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ApplyConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-config-failed

mibFaultCode: 79496

mibFaultName: fsmRmtErrSmLogicalDeviceConfigureApplyConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmRmtErrSmLogicalDeviceConfigure:AutoConfig

Fault Code: F79496

Message

[FSM:STAGE:REMOTE-ERROR]: Auto configure external port link.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:AutoConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: auto-config-failed

mibFaultCode: 79496

mibFaultName: fsmRmtErrSmLogicalDeviceConfigureAutoConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmRmtErrSmLogicalDeviceConfigure:CheckConfigIssues

Fault Code: F79496

Message

[FSM:STAGE:REMOTE-ERROR]: Check logical device configuration issues.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:CheckConfigIssues)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-config-issues-failed

mibFaultCode: 79496

mibFaultName: fsmRmtErrSmLogicalDeviceConfigureCheckConfigIssues

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmRmtErrSmLogicalDeviceConfigure:ResolvePolicy

Fault Code: F79496

Message

[FSM:STAGE:REMOTE-ERROR]: Resolve policy and external MO reference.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ResolvePolicy)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: resolve-policy-failed

mibFaultCode: 79496

mibFaultName: fsmRmtErrSmLogicalDeviceConfigureResolvePolicy

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmRmtErrSmLogicalDeviceConfigure:ValidateLDConfig

Fault Code: F79496

Message

[FSM:STAGE:REMOTE-ERROR]: Validate logical device configuration.(FSM-STAGE:sam:dme:SmLogicalDeviceConfigure:ValidateLDConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: validateldconfig-failed

mibFaultCode: 79496

mibFaultName: fsmRmtErrSmLogicalDeviceConfigureValidateLDConfig

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmRmtErrSdLduUpdateInterfaceStatus:SendStatus

Fault Code: F79498

Message

[FSM:STAGE:REMOTE-ERROR]: Send Interface Operational State(FSM-STAGE:sam:dme:SdLduUpdateInterfaceStatus:SendStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-status-failed

mibFaultCode: 79498

mibFaultName: fsmRmtErrSdLduUpdateInterfaceStatusSendStatus

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmRmtErrSdLogicalDeviceConfigureUserMacs:ConfigureSwitch

Fault Code: F79499

Message

[FSM:STAGE:REMOTE-ERROR]: Invoke Port API to configure the switch(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureUserMacs:ConfigureSwitch)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-switch-failed

mibFaultCode: 79499

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureUserMacsConfigureSwitch

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrSdLogicalDeviceConfigureUserMacs:WaitForSwitchConfig

Fault Code: F79499

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for Switch configuration to complete(FSM-STAGE:sam:dme:SdLogicalDeviceConfigureUserMacs:WaitForSwitchConfig)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-switch-config-failed

mibFaultCode: 79499

mibFaultName: fsmRmtErrSdLogicalDeviceConfigureUserMacsWaitForSwitchConfig

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmRmtErrEquipmentChassisRebootChassis:ApplyReboot

Fault Code: F79500

Message

[FSM:STAGE:REMOTE-ERROR]: Reboot Chassis(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:ApplyReboot)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: apply-reboot-failed

mibFaultCode: 79500

mibFaultName: fsmRmtErrEquipmentChassisRebootChassisApplyReboot

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRebootChassis:DebundlePort

Fault Code: F79500

Message

[FSM:STAGE:REMOTE-ERROR]: Debundle the ports(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:DebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: debundle-port-failed

mibFaultCode: 79500

mibFaultName: fsmRmtErrEquipmentChassisRebootChassisDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRebootChassis:PollDebundlePort

Fault Code: F79500

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for Ports debundle complete(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:PollDebundlePort)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: poll-debundle-port-failed

mibFaultCode: 79500

mibFaultName: fsmRmtErrEquipmentChassisRebootChassisPollDebundlePort

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRebootChassis:ShutdownBlade

Fault Code: F79500

Message

[FSM:STAGE:REMOTE-ERROR]: Shutdown Blade(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:ShutdownBlade)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: shutdown-blade-failed

mibFaultCode: 79500

mibFaultName: fsmRmtErrEquipmentChassisRebootChassisShutdownBlade

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrEquipmentChassisRebootChassis:WaitForBladeShutdown

Fault Code: F79500

Message

[FSM:STAGE:REMOTE-ERROR]: Waiting for blade shutdown(FSM-STAGE:sam:dme:EquipmentChassisRebootChassis:WaitForBladeShutdown)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-blade-shutdown-failed

mibFaultCode: 79500

mibFaultName: fsmRmtErrEquipmentChassisRebootChassisWaitForBladeShutdown

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmRmtErrFirmwareValidationStatusValidate:CheckReadiness

Fault Code: F79504

Message

[FSM:STAGE:REMOTE-ERROR]: Image validation queued(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:CheckReadiness)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: check-readiness-failed

mibFaultCode: 79504

mibFaultName: fsmRmtErrFirmwareValidationStatusValidateCheckReadiness

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmRmtErrFirmwareValidationStatusValidate:Complete

Fault Code: F79504

Message

[FSM:STAGE:REMOTE-ERROR]: Complete Validation(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:Complete)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: complete-failed

mibFaultCode: 79504

mibFaultName: fsmRmtErrFirmwareValidationStatusValidateComplete

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmRmtErrFirmwareValidationStatusValidate:PlatformPack

Fault Code: F79504

Message

[FSM:STAGE:REMOTE-ERROR]: Validating the platform pack(FSM-STAGE:sam:dme:FirmwareValidationStatusValidate:PlatformPack)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: platform-pack-failed

mibFaultCode: 79504

mibFaultName: fsmRmtErrFirmwareValidationStatusValidatePlatformPack

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmRmtErrSdPortsBundleBundleDataPorts:ConfigureLinks

Fault Code: F79521

Message

[FSM:STAGE:REMOTE-ERROR]: Trigger ConfigureLinks FSM(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:ConfigureLinks)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: configure-links-failed

mibFaultCode: 79521

mibFaultName: fsmRmtErrSdPortsBundleBundleDataPortsConfigureLinks

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmRmtErrSdPortsBundleBundleDataPorts:SendBundleStatus

Fault Code: F79521

Message

[FSM:STAGE:REMOTE-ERROR]: Notify Application about Port Bundle Status(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:SendBundleStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: send-bundle-status-failed

mibFaultCode: 79521

mibFaultName: fsmRmtErrSdPortsBundleBundleDataPortsSendBundleStatus

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmRmtErrSdPortsBundleBundleDataPorts:UpdateBundleStatus

Fault Code: F79521

Message

[FSM:STAGE:REMOTE-ERROR]: Update the bundle status(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:UpdateBundleStatus)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-bundle-status-failed

mibFaultCode: 79521

mibFaultName: fsmRmtErrSdPortsBundleBundleDataPortsUpdateBundleStatus

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmRmtErrSdPortsBundleBundleDataPorts:WaitForConfigCompletion

Fault Code: F79521

Message

[FSM:STAGE:REMOTE-ERROR]: Wait for links configuration completion(FSM-STAGE:sam:dme:SdPortsBundleBundleDataPorts:WaitForConfigCompletion)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: wait-for-config-completion-failed

mibFaultCode: 79521

mibFaultName: fsmRmtErrSdPortsBundleBundleDataPortsWaitForConfigCompletion

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmRmtErrSdHotfixInstallHotfix:Install

Fault Code: F79522

Message

[FSM:STAGE:REMOTE-ERROR]: Install hotfix(FSM-STAGE:sam:dme:SdHotfixInstallHotfix:Install)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: install-failed

mibFaultCode: 79522

mibFaultName: fsmRmtErrSdHotfixInstallHotfixInstall

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmRmtErrSdHotfixInstallHotfix:UpdateHotfix

Fault Code: F79522

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the state of hotifx(FSM-STAGE:sam:dme:SdHotfixInstallHotfix:UpdateHotfix)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-hotfix-failed

mibFaultCode: 79522

mibFaultName: fsmRmtErrSdHotfixInstallHotfixUpdateHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmRmtErrSdHotfixUninstallHotfix:Uninstall

Fault Code: F79523

Message

[FSM:STAGE:REMOTE-ERROR]: Uninstall hotfix(FSM-STAGE:sam:dme:SdHotfixUninstallHotfix:Uninstall)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: uninstall-failed

mibFaultCode: 79523

mibFaultName: fsmRmtErrSdHotfixUninstallHotfixUninstall

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmRmtErrSdHotfixUninstallHotfix:UpdateHotfix

Fault Code: F79523

Message

[FSM:STAGE:REMOTE-ERROR]: Updates the state of hotifx(FSM-STAGE:sam:dme:SdHotfixUninstallHotfix:UpdateHotfix)

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: warning

Cause: update-hotfix-failed

mibFaultCode: 79523

mibFaultName: fsmRmtErrSdHotfixUninstallHotfixUpdateHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmFailEquipmentChassisRemoveChassis

Fault Code: F999447

Message

[FSM:FAILED]: sam:dme:EquipmentChassisRemoveChassis

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999447

mibFaultName: fsmFailEquipmentChassisRemoveChassis

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailEquipmentLocatorLedSetLocatorLed

Fault Code: F999448

Message

[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetLocatorLed

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999448

mibFaultName: fsmFailEquipmentLocatorLedSetLocatorLed

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmFailMgmtControllerExtMgmtIfConfig

Fault Code: F999558

Message

[FSM:FAILED]: sam:dme:MgmtControllerExtMgmtIfConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999558

mibFaultName: fsmFailMgmtControllerExtMgmtIfConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailFabricComputeSlotEpIdentify

Fault Code: F999559

Message

[FSM:FAILED]: sam:dme:FabricComputeSlotEpIdentify

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999559

mibFaultName: fsmFailFabricComputeSlotEpIdentify

moClass: fabric:ComputeSlotEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

fsmFailComputeBladeDiscover

Fault Code: F999560

Message

[FSM:FAILED]: sam:dme:ComputeBladeDiscover

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999560

mibFaultName: fsmFailComputeBladeDiscover

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmFailEquipmentChassisPsuPolicyConfig

Fault Code: F999573

Message

[FSM:FAILED]: sam:dme:EquipmentChassisPsuPolicyConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999573

mibFaultName: fsmFailEquipmentChassisPsuPolicyConfig

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailAdaptorHostFcIfResetFcPersBinding

Fault Code: F999574

Message

[FSM:FAILED]: sam:dme:AdaptorHostFcIfResetFcPersBinding

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999574

mibFaultName: fsmFailAdaptorHostFcIfResetFcPersBinding

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmFailComputeBladeDiag

Fault Code: F999575

Message

[FSM:FAILED]: sam:dme:ComputeBladeDiag

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999575

mibFaultName: fsmFailComputeBladeDiag

moClass: compute:Blade

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

fsmFailFabricLanCloudSwitchMode

Fault Code: F999579

Message

[FSM:FAILED]: sam:dme:FabricLanCloudSwitchMode

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999579

mibFaultName: fsmFailFabricLanCloudSwitchMode

moClass: fabric:LanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan

fsmFailVnicProfileSetDeploy

Fault Code: F999590

Message

[FSM:FAILED]: sam:dme:VnicProfileSetDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999590

mibFaultName: fsmFailVnicProfileSetDeploy

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmFailCommSvcEpUpdateSvcEp

Fault Code: F999616

Message

[FSM:FAILED]: sam:dme:CommSvcEpUpdateSvcEp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999616

mibFaultName: fsmFailCommSvcEpUpdateSvcEp

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmFailCommSvcEpRestartWebSvc

Fault Code: F999617

Message

[FSM:FAILED]: sam:dme:CommSvcEpRestartWebSvc

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999617

mibFaultName: fsmFailCommSvcEpRestartWebSvc

moClass: comm:SvcEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/svc-ext

fsmFailAaaEpUpdateEp

Fault Code: F999619

Message

[FSM:FAILED]: sam:dme:AaaEpUpdateEp

Explanation

Cisco FPR Manager could not set the configurations for AAA servers.

Recommended Action

Check the error for the failed FSM stage and take the recommended action for that stage.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999619

mibFaultName: fsmFailAaaEpUpdateEp

moClass: aaa:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ldap-ext

Affected MO: sys/radius-ext

Affected MO: sys/tacacs-ext

fsmFailAaaRealmUpdateRealm

Fault Code: F999620

Message

[FSM:FAILED]: sam:dme:AaaRealmUpdateRealm

Explanation

Cisco FPR Manager could not set the configurations for Authentication Realm.

Recommended Action

Check the error for the failed FSM stage and take the recommended action for that stage.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999620

mibFaultName: fsmFailAaaRealmUpdateRealm

moClass: aaa:Realm

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/auth-realm

fsmFailAaaUserEpUpdateUserEp

Fault Code: F999621

Message

[FSM:FAILED]: sam:dme:AaaUserEpUpdateUserEp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999621

mibFaultName: fsmFailAaaUserEpUpdateUserEp

moClass: aaa:UserEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/user-ext

fsmFailPkiEpUpdateEp

Fault Code: F999622

Message

[FSM:FAILED]: sam:dme:PkiEpUpdateEp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999622

mibFaultName: fsmFailPkiEpUpdateEp

moClass: pki:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/pki-ext

fsmFailSysfileMutationSingle

Fault Code: F999640

Message

[FSM:FAILED]: sam:dme:SysfileMutationSingle

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999640

mibFaultName: fsmFailSysfileMutationSingle

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmFailSysfileMutationGlobal

Fault Code: F999641

Message

[FSM:FAILED]: sam:dme:SysfileMutationGlobal

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999641

mibFaultName: fsmFailSysfileMutationGlobal

moClass: sysfile:Mutation

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/mutation

Affected MO: sys/corefiles/mutation

fsmFailSysdebugManualCoreFileExportTargetExport

Fault Code: F999644

Message

[FSM:FAILED]: sam:dme:SysdebugManualCoreFileExportTargetExport

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999644

mibFaultName: fsmFailSysdebugManualCoreFileExportTargetExport

moClass: sysdebug:ManualCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]/export-to-[hostname]

fsmFailSysdebugAutoCoreFileExportTargetConfigure

Fault Code: F999645

Message

[FSM:FAILED]: sam:dme:SysdebugAutoCoreFileExportTargetConfigure

Explanation

Cisco Firepower Manager could not set the configurations for auto core transfer to remote TFTP server.

Recommended Action

Check the error for the failed FSM stage and take the recommended action for that stage.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999645

mibFaultName: fsmFailSysdebugAutoCoreFileExportTargetConfigure

moClass: sysdebug:AutoCoreFileExportTarget

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/file-export

fsmFailSysdebugLogControlEpLogControlPersist

Fault Code: F999646

Message

[FSM:FAILED]: sam:dme:SysdebugLogControlEpLogControlPersist

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999646

mibFaultName: fsmFailSysdebugLogControlEpLogControlPersist

moClass: sysdebug:LogControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/logcontrol

fsmFailSwAccessDomainDeploy

Fault Code: F999674

Message

[FSM:FAILED]: sam:dme:SwAccessDomainDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999674

mibFaultName: fsmFailSwAccessDomainDeploy

moClass: sw:AccessDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/access-eth

fsmFailSwEthLanBorderDeploy

Fault Code: F999675

Message

[FSM:FAILED]: sam:dme:SwEthLanBorderDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999675

mibFaultName: fsmFailSwEthLanBorderDeploy

moClass: sw:EthLanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-eth

fsmFailSwFcSanBorderDeploy

Fault Code: F999676

Message

[FSM:FAILED]: sam:dme:SwFcSanBorderDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999676

mibFaultName: fsmFailSwFcSanBorderDeploy

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmFailSwUtilityDomainDeploy

Fault Code: F999677

Message

[FSM:FAILED]: sam:dme:SwUtilityDomainDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999677

mibFaultName: fsmFailSwUtilityDomainDeploy

moClass: sw:UtilityDomain

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/utility-eth

fsmFailSyntheticFsObjCreate

Fault Code: F999681

Message

[FSM:FAILED]: sam:dme:SyntheticFsObjCreate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999681

mibFaultName: fsmFailSyntheticFsObjCreate

moClass: synthetic:FsObj

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/file-[name]

fsmFailFirmwareDownloaderDownload

Fault Code: F999690

Message

[FSM:FAILED]: sam:dme:FirmwareDownloaderDownload

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999690

mibFaultName: fsmFailFirmwareDownloaderDownload

moClass: firmware:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/dnld-[fileName]

Affected MO: sys/pki-ext/tp-[name]/certrevoke/dnld-[fileName]

fsmFailFirmwareImageDelete

Fault Code: F999691

Message

[FSM:FAILED]: sam:dme:FirmwareImageDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999691

mibFaultName: fsmFailFirmwareImageDelete

moClass: firmware:Image

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/image-[name]

Affected MO: sys/fw-catalogue/image-[name]

fsmFailMgmtControllerUpdateSwitch

Fault Code: F999693

Message

[FSM:FAILED]: sam:dme:MgmtControllerUpdateSwitch

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999693

mibFaultName: fsmFailMgmtControllerUpdateSwitch

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailMgmtControllerUpdateIOM

Fault Code: F999694

Message

[FSM:FAILED]: sam:dme:MgmtControllerUpdateIOM

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999694

mibFaultName: fsmFailMgmtControllerUpdateIOM

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailMgmtControllerActivateIOM

Fault Code: F999695

Message

[FSM:FAILED]: sam:dme:MgmtControllerActivateIOM

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999695

mibFaultName: fsmFailMgmtControllerActivateIOM

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailMgmtControllerUpdateBMC

Fault Code: F999696

Message

[FSM:FAILED]: sam:dme:MgmtControllerUpdateBMC

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999696

mibFaultName: fsmFailMgmtControllerUpdateBMC

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailMgmtControllerActivateBMC

Fault Code: F999697

Message

[FSM:FAILED]: sam:dme:MgmtControllerActivateBMC

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999697

mibFaultName: fsmFailMgmtControllerActivateBMC

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailCallhomeEpConfigCallhome

Fault Code: F999710

Message

[FSM:FAILED]: sam:dme:CallhomeEpConfigCallhome

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999710

mibFaultName: fsmFailCallhomeEpConfigCallhome

moClass: callhome:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: call-home

fsmFailMgmtIfSwMgmtOobIfConfig

Fault Code: F999713

Message

[FSM:FAILED]: sam:dme:MgmtIfSwMgmtOobIfConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999713

mibFaultName: fsmFailMgmtIfSwMgmtOobIfConfig

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtIfSwMgmtInbandIfConfig

Fault Code: F999714

Message

[FSM:FAILED]: sam:dme:MgmtIfSwMgmtInbandIfConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999714

mibFaultName: fsmFailMgmtIfSwMgmtInbandIfConfig

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtIfVirtualIfConfig

Fault Code: F999719

Message

[FSM:FAILED]: sam:dme:MgmtIfVirtualIfConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999719

mibFaultName: fsmFailMgmtIfVirtualIfConfig

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtIfEnableVip

Fault Code: F999720

Message

[FSM:FAILED]: sam:dme:MgmtIfEnableVip

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999720

mibFaultName: fsmFailMgmtIfEnableVip

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtIfDisableVip

Fault Code: F999721

Message

[FSM:FAILED]: sam:dme:MgmtIfDisableVip

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999721

mibFaultName: fsmFailMgmtIfDisableVip

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtIfEnableHA

Fault Code: F999722

Message

[FSM:FAILED]: sam:dme:MgmtIfEnableHA

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999722

mibFaultName: fsmFailMgmtIfEnableHA

moClass: mgmt:If

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/mgmt/if-[id]

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]

Affected MO: sys/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]

Affected MO: sys/switch-[id]/mgmt/if-[id]

fsmFailMgmtBackupBackup

Fault Code: F999723

Message

[FSM:FAILED]: sam:dme:MgmtBackupBackup

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999723

mibFaultName: fsmFailMgmtBackupBackup

moClass: mgmt:Backup

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/backup-[hostname]

fsmFailMgmtImporterImport

Fault Code: F999724

Message

[FSM:FAILED]: sam:dme:MgmtImporterImport

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999724

mibFaultName: fsmFailMgmtImporterImport

moClass: mgmt:Importer

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/import-config-[hostname]

fsmFailStatsCollectionPolicyUpdateEp

Fault Code: F999782

Message

[FSM:FAILED]: sam:dme:StatsCollectionPolicyUpdateEp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999782

mibFaultName: fsmFailStatsCollectionPolicyUpdateEp

moClass: stats:CollectionPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: stats/coll-policy-[name]

fsmFailQosclassDefinitionConfigGlobalQoS

Fault Code: F999785

Message

[FSM:FAILED]: sam:dme:QosclassDefinitionConfigGlobalQoS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999785

mibFaultName: fsmFailQosclassDefinitionConfigGlobalQoS

moClass: qosclass:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/classes

fsmFailEpqosDefinitionDeploy

Fault Code: F999789

Message

[FSM:FAILED]: sam:dme:EpqosDefinitionDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999789

mibFaultName: fsmFailEpqosDefinitionDeploy

moClass: epqos:Definition

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-[name]

fsmFailEpqosDefinitionDelTaskRemove

Fault Code: F999790

Message

[FSM:FAILED]: sam:dme:EpqosDefinitionDelTaskRemove

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999790

mibFaultName: fsmFailEpqosDefinitionDelTaskRemove

moClass: epqos:DefinitionDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ep-qos-deletion-[defIntId]

fsmFailEquipmentIOCardResetCmc

Fault Code: F999843

Message

[FSM:FAILED]: sam:dme:EquipmentIOCardResetCmc

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999843

mibFaultName: fsmFailEquipmentIOCardResetCmc

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmFailMgmtControllerUpdateUCSManager

Fault Code: F999855

Message

[FSM:FAILED]: sam:dme:MgmtControllerUpdateUCSManager

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999855

mibFaultName: fsmFailMgmtControllerUpdateUCSManager

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailMgmtControllerSysConfig

Fault Code: F999863

Message

[FSM:FAILED]: sam:dme:MgmtControllerSysConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999863

mibFaultName: fsmFailMgmtControllerSysConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailAdaptorExtEthIfPathReset

Fault Code: F999892

Message

[FSM:FAILED]: sam:dme:AdaptorExtEthIfPathReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999892

mibFaultName: fsmFailAdaptorExtEthIfPathReset

moClass: adaptor:ExtEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fsmFailAdaptorHostEthIfCircuitReset

Fault Code: F999897

Message

[FSM:FAILED]: sam:dme:AdaptorHostEthIfCircuitReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999897

mibFaultName: fsmFailAdaptorHostEthIfCircuitReset

moClass: adaptor:HostEthIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fsmFailAdaptorHostFcIfCircuitReset

Fault Code: F999898

Message

[FSM:FAILED]: sam:dme:AdaptorHostFcIfCircuitReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999898

mibFaultName: fsmFailAdaptorHostFcIfCircuitReset

moClass: adaptor:HostFcIf

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]

fsmFailExtvmmProviderConfig

Fault Code: F999919

Message

[FSM:FAILED]: sam:dme:ExtvmmProviderConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999919

mibFaultName: fsmFailExtvmmProviderConfig

moClass: extvmm:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vm-[name]

fsmFailExtvmmKeyStoreCertInstall

Fault Code: F999920

Message

[FSM:FAILED]: sam:dme:ExtvmmKeyStoreCertInstall

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999920

mibFaultName: fsmFailExtvmmKeyStoreCertInstall

moClass: extvmm:KeyStore

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/key-store

fsmFailExtvmmSwitchDelTaskRemoveProvider

Fault Code: F999921

Message

[FSM:FAILED]: sam:dme:ExtvmmSwitchDelTaskRemoveProvider

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999921

mibFaultName: fsmFailExtvmmSwitchDelTaskRemoveProvider

moClass: extvmm:SwitchDelTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/vsw-deltask-[swIntId]

fsmFailExtvmmMasterExtKeyConfig

Fault Code: F999938

Message

[FSM:FAILED]: sam:dme:ExtvmmMasterExtKeyConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999938

mibFaultName: fsmFailExtvmmMasterExtKeyConfig

moClass: extvmm:MasterExtKey

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt/ext-key

fsmFailCapabilityUpdaterUpdater

Fault Code: F999944

Message

[FSM:FAILED]: sam:dme:CapabilityUpdaterUpdater

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999944

mibFaultName: fsmFailCapabilityUpdaterUpdater

moClass: capability:Updater

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/updater-[fileName]

fsmFailFirmwareDistributableDelete

Fault Code: F999946

Message

[FSM:FAILED]: sam:dme:FirmwareDistributableDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999946

mibFaultName: fsmFailFirmwareDistributableDelete

moClass: firmware:Distributable

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]

fsmFailCapabilityCatalogueDeployCatalogue

Fault Code: F999971

Message

[FSM:FAILED]: sam:dme:CapabilityCatalogueDeployCatalogue

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999971

mibFaultName: fsmFailCapabilityCatalogueDeployCatalogue

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmFailEquipmentFexRemoveFex

Fault Code: F999982

Message

[FSM:FAILED]: sam:dme:EquipmentFexRemoveFex

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999982

mibFaultName: fsmFailEquipmentFexRemoveFex

moClass: equipment:Fex

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fex-[id]

fsmFailEquipmentLocatorLedSetFeLocatorLed

Fault Code: F999983

Message

[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetFeLocatorLed

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999983

mibFaultName: fsmFailEquipmentLocatorLedSetFeLocatorLed

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmFailEquipmentChassisPowerCap

Fault Code: F999984

Message

[FSM:FAILED]: sam:dme:EquipmentChassisPowerCap

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999984

mibFaultName: fsmFailEquipmentChassisPowerCap

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailEquipmentIOCardMuxOffline

Fault Code: F999985

Message

[FSM:FAILED]: sam:dme:EquipmentIOCardMuxOffline

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999985

mibFaultName: fsmFailEquipmentIOCardMuxOffline

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmFailComputePhysicalAssociate

Fault Code: F1000013

Message

[FSM:FAILED]: sam:dme:ComputePhysicalAssociate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000013

mibFaultName: fsmFailComputePhysicalAssociate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalDisassociate

Fault Code: F1000014

Message

[FSM:FAILED]: sam:dme:ComputePhysicalDisassociate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000014

mibFaultName: fsmFailComputePhysicalDisassociate

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalPowerCap

Fault Code: F1000015

Message

[FSM:FAILED]: sam:dme:ComputePhysicalPowerCap

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000015

mibFaultName: fsmFailComputePhysicalPowerCap

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalDecommission

Fault Code: F1000016

Message

[FSM:FAILED]: sam:dme:ComputePhysicalDecommission

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000016

mibFaultName: fsmFailComputePhysicalDecommission

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalSoftShutdown

Fault Code: F1000017

Message

[FSM:FAILED]: sam:dme:ComputePhysicalSoftShutdown

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000017

mibFaultName: fsmFailComputePhysicalSoftShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalHardShutdown

Fault Code: F1000018

Message

[FSM:FAILED]: sam:dme:ComputePhysicalHardShutdown

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000018

mibFaultName: fsmFailComputePhysicalHardShutdown

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalTurnup

Fault Code: F1000019

Message

[FSM:FAILED]: sam:dme:ComputePhysicalTurnup

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000019

mibFaultName: fsmFailComputePhysicalTurnup

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalPowercycle

Fault Code: F1000020

Message

[FSM:FAILED]: sam:dme:ComputePhysicalPowercycle

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000020

mibFaultName: fsmFailComputePhysicalPowercycle

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalHardreset

Fault Code: F1000021

Message

[FSM:FAILED]: sam:dme:ComputePhysicalHardreset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000021

mibFaultName: fsmFailComputePhysicalHardreset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalSoftreset

Fault Code: F1000022

Message

[FSM:FAILED]: sam:dme:ComputePhysicalSoftreset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000022

mibFaultName: fsmFailComputePhysicalSoftreset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalSwConnUpd

Fault Code: F1000023

Message

[FSM:FAILED]: sam:dme:ComputePhysicalSwConnUpd

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000023

mibFaultName: fsmFailComputePhysicalSwConnUpd

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalBiosRecovery

Fault Code: F1000024

Message

[FSM:FAILED]: sam:dme:ComputePhysicalBiosRecovery

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000024

mibFaultName: fsmFailComputePhysicalBiosRecovery

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalCmosReset

Fault Code: F1000026

Message

[FSM:FAILED]: sam:dme:ComputePhysicalCmosReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000026

mibFaultName: fsmFailComputePhysicalCmosReset

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalResetBmc

Fault Code: F1000027

Message

[FSM:FAILED]: sam:dme:ComputePhysicalResetBmc

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000027

mibFaultName: fsmFailComputePhysicalResetBmc

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailEquipmentIOCardResetIom

Fault Code: F1000028

Message

[FSM:FAILED]: sam:dme:EquipmentIOCardResetIom

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000028

mibFaultName: fsmFailEquipmentIOCardResetIom

moClass: equipment:IOCard

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmFailComputeRackUnitDiscover

Fault Code: F1000034

Message

[FSM:FAILED]: sam:dme:ComputeRackUnitDiscover

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000034

mibFaultName: fsmFailComputeRackUnitDiscover

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmFailLsServerConfigure

Fault Code: F1000035

Message

[FSM:FAILED]: sam:dme:LsServerConfigure

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000035

mibFaultName: fsmFailLsServerConfigure

moClass: ls:Server

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/ls-[name]

Affected MO: org-[name]/tier-[name]/ls-[name]

fsmFailSwEthMonDeploy

Fault Code: F1000040

Message

[FSM:FAILED]: sam:dme:SwEthMonDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000040

mibFaultName: fsmFailSwEthMonDeploy

moClass: sw:EthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]

fsmFailSwFcMonDeploy

Fault Code: F1000041

Message

[FSM:FAILED]: sam:dme:SwFcMonDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000041

mibFaultName: fsmFailSwFcMonDeploy

moClass: sw:FcMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/sanmon-fc/mon-[name]

fsmFailFabricSanCloudSwitchMode

Fault Code: F1000042

Message

[FSM:FAILED]: sam:dme:FabricSanCloudSwitchMode

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000042

mibFaultName: fsmFailFabricSanCloudSwitchMode

moClass: fabric:SanCloud

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/san

fsmFailComputePhysicalUpdateExtUsers

Fault Code: F1000048

Message

[FSM:FAILED]: sam:dme:ComputePhysicalUpdateExtUsers

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000048

mibFaultName: fsmFailComputePhysicalUpdateExtUsers

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailSysdebugTechSupportInitiate

Fault Code: F1000052

Message

[FSM:FAILED]: sam:dme:SysdebugTechSupportInitiate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000052

mibFaultName: fsmFailSysdebugTechSupportInitiate

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmFailSysdebugTechSupportDeleteTechSupFile

Fault Code: F1000053

Message

[FSM:FAILED]: sam:dme:SysdebugTechSupportDeleteTechSupFile

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000053

mibFaultName: fsmFailSysdebugTechSupportDeleteTechSupFile

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmFailSysdebugTechSupportDownload

Fault Code: F1000054

Message

[FSM:FAILED]: sam:dme:SysdebugTechSupportDownload

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000054

mibFaultName: fsmFailSysdebugTechSupportDownload

moClass: sysdebug:TechSupport

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tech-support-files/tech-support-[creationTS]

fsmFailComputePhysicalUpdateAdaptor

Fault Code: F1000083

Message

[FSM:FAILED]: sam:dme:ComputePhysicalUpdateAdaptor

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000083

mibFaultName: fsmFailComputePhysicalUpdateAdaptor

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalActivateAdaptor

Fault Code: F1000084

Message

[FSM:FAILED]: sam:dme:ComputePhysicalActivateAdaptor

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000084

mibFaultName: fsmFailComputePhysicalActivateAdaptor

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailCapabilityCatalogueActivateCatalog

Fault Code: F1000085

Message

[FSM:FAILED]: sam:dme:CapabilityCatalogueActivateCatalog

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000085

mibFaultName: fsmFailCapabilityCatalogueActivateCatalog

moClass: capability:Catalogue

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities

fsmFailCapabilityMgmtExtensionActivateMgmtExt

Fault Code: F1000086

Message

[FSM:FAILED]: sam:dme:CapabilityMgmtExtensionActivateMgmtExt

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000086

mibFaultName: fsmFailCapabilityMgmtExtensionActivateMgmtExt

moClass: capability:MgmtExtension

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: capabilities/ep/mgmt-ext

fsmFailLicenseDownloaderDownload

Fault Code: F1000090

Message

[FSM:FAILED]: sam:dme:LicenseDownloaderDownload

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000090

mibFaultName: fsmFailLicenseDownloaderDownload

moClass: license:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/dnld-[fileName]

fsmFailLicenseFileInstall

Fault Code: F1000091

Message

[FSM:FAILED]: sam:dme:LicenseFileInstall

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000091

mibFaultName: fsmFailLicenseFileInstall

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmFailLicenseFileClear

Fault Code: F1000092

Message

[FSM:FAILED]: sam:dme:LicenseFileClear

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000092

mibFaultName: fsmFailLicenseFileClear

moClass: license:File

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/file-[scope]:[id]

fsmFailLicenseInstanceUpdateFlexlm

Fault Code: F1000093

Message

[FSM:FAILED]: sam:dme:LicenseInstanceUpdateFlexlm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000093

mibFaultName: fsmFailLicenseInstanceUpdateFlexlm

moClass: license:Instance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fsmFailComputePhysicalConfigSoL

Fault Code: F1000123

Message

[FSM:FAILED]: sam:dme:ComputePhysicalConfigSoL

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000123

mibFaultName: fsmFailComputePhysicalConfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalUnconfigSoL

Fault Code: F1000124

Message

[FSM:FAILED]: sam:dme:ComputePhysicalUnconfigSoL

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000124

mibFaultName: fsmFailComputePhysicalUnconfigSoL

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailPortPIoInCompatSfpPresence

Fault Code: F1000129

Message

[FSM:FAILED]: sam:dme:PortPIoInCompatSfpPresence

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000129

mibFaultName: fsmFailPortPIoInCompatSfpPresence

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmFailComputePhysicalDiagnosticInterrupt

Fault Code: F1000156

Message

[FSM:FAILED]: sam:dme:ComputePhysicalDiagnosticInterrupt

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000156

mibFaultName: fsmFailComputePhysicalDiagnosticInterrupt

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailSysdebugCoreDownload

Fault Code: F1000173

Message

[FSM:FAILED]: sam:dme:SysdebugCoreDownload

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000173

mibFaultName: fsmFailSysdebugCoreDownload

moClass: sysdebug:Core

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/corefiles/file-[name]|[switchId]

fsmFailEquipmentChassisDynamicReallocation

Fault Code: F1000174

Message

[FSM:FAILED]: sam:dme:EquipmentChassisDynamicReallocation

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000174

mibFaultName: fsmFailEquipmentChassisDynamicReallocation

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailComputePhysicalResetKvm

Fault Code: F1000203

Message

[FSM:FAILED]: sam:dme:ComputePhysicalResetKvm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000203

mibFaultName: fsmFailComputePhysicalResetKvm

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailMgmtControllerOnline

Fault Code: F1000209

Message

[FSM:FAILED]: sam:dme:MgmtControllerOnline

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000209

mibFaultName: fsmFailMgmtControllerOnline

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailComputeRackUnitOffline

Fault Code: F1000210

Message

[FSM:FAILED]: sam:dme:ComputeRackUnitOffline

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000210

mibFaultName: fsmFailComputeRackUnitOffline

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmFailEquipmentLocatorLedSetFiLocatorLed

Fault Code: F1000227

Message

[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetFiLocatorLed

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000227

mibFaultName: fsmFailEquipmentLocatorLedSetFiLocatorLed

moClass: equipment:LocatorLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/locator-led

Affected MO: sys/chassis-[id]/blade-[slotId]/locator-led

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/chassis-[id]/locator-led

Affected MO: sys/chassis-[id]/psu-[id]/locator-led

Affected MO: sys/chassis-[id]/slot-[id]/locator-led

Affected MO: sys/fex-[id]/locator-led

Affected MO: sys/fex-[id]/psu-[id]/locator-led

Affected MO: sys/fex-[id]/slot-[id]/locator-led

Affected MO: sys/rack-unit-[id]/ext-board-[id]/locator-led

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/rack-unit-[id]/locator-led

Affected MO: sys/rack-unit-[id]/psu-[id]/locator-led

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/locator-led

Affected MO: sys/switch-[id]/locator-led

Affected MO: sys/switch-[id]/psu-[id]/locator-led

fsmFailFabricEpMgrConfigure

Fault Code: F1000254

Message

[FSM:FAILED]: sam:dme:FabricEpMgrConfigure

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000254

mibFaultName: fsmFailFabricEpMgrConfigure

moClass: fabric:EpMgr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/[id]

fsmFailVnicProfileSetDeployAlias

Fault Code: F1000263

Message

[FSM:FAILED]: sam:dme:VnicProfileSetDeployAlias

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000263

mibFaultName: fsmFailVnicProfileSetDeployAlias

moClass: vnic:ProfileSet

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/profiles

fsmFailSwPhysConfPhysical

Fault Code: F1000279

Message

[FSM:FAILED]: sam:dme:SwPhysConfPhysical

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000279

mibFaultName: fsmFailSwPhysConfPhysical

moClass: sw:Phys

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/phys

fsmFailExtvmmEpClusterRole

Fault Code: F1000294

Message

[FSM:FAILED]: sam:dme:ExtvmmEpClusterRole

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000294

mibFaultName: fsmFailExtvmmEpClusterRole

moClass: extvmm:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/extvm-mgmt

fsmFailVmLifeCyclePolicyConfig

Fault Code: F1000299

Message

[FSM:FAILED]: sam:dme:VmLifeCyclePolicyConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000299

mibFaultName: fsmFailVmLifeCyclePolicyConfig

moClass: vm:LifeCyclePolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/vm-lc-policy

fsmFailEquipmentBeaconLedIlluminate

Fault Code: F1000302

Message

[FSM:FAILED]: sam:dme:EquipmentBeaconLedIlluminate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000302

mibFaultName: fsmFailEquipmentBeaconLedIlluminate

moClass: equipment:BeaconLed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/beacon

Affected MO: sys/chassis-[id]/blade-[slotId]/beacon

Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/chassis-[id]/psu-[id]/beacon

Affected MO: sys/chassis-[id]/slot-[id]/beacon

Affected MO: sys/fex-[id]/beacon

Affected MO: sys/fex-[id]/psu-[id]/beacon

Affected MO: sys/fex-[id]/slot-[id]/beacon

Affected MO: sys/rack-unit-[id]/beacon

Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/rack-unit-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/beacon

Affected MO: sys/switch-[id]/psu-[id]/beacon

Affected MO: sys/switch-[id]/slot-[id]/beacon

fsmFailEtherServerIntFIoConfigSpeed

Fault Code: F1000311

Message

[FSM:FAILED]: sam:dme:EtherServerIntFIoConfigSpeed

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000311

mibFaultName: fsmFailEtherServerIntFIoConfigSpeed

moClass: ether:ServerIntFIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/rack-unit-[id]/diag/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmFailComputePhysicalUpdateBIOS

Fault Code: F1000321

Message

[FSM:FAILED]: sam:dme:ComputePhysicalUpdateBIOS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000321

mibFaultName: fsmFailComputePhysicalUpdateBIOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalActivateBIOS

Fault Code: F1000322

Message

[FSM:FAILED]: sam:dme:ComputePhysicalActivateBIOS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000322

mibFaultName: fsmFailComputePhysicalActivateBIOS

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailIdentIdentRequestUpdateIdent

Fault Code: F1000352

Message

[FSM:FAILED]: sam:dme:IdentIdentRequestUpdateIdent

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000352

mibFaultName: fsmFailIdentIdentRequestUpdateIdent

moClass: ident:IdentRequest

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys/IdentQ-[id]

fsmFailIdentMetaSystemSync

Fault Code: F1000353

Message

[FSM:FAILED]: sam:dme:IdentMetaSystemSync

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000353

mibFaultName: fsmFailIdentMetaSystemSync

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmFailComputePhysicalResetIpmi

Fault Code: F1000366

Message

[FSM:FAILED]: sam:dme:ComputePhysicalResetIpmi

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000366

mibFaultName: fsmFailComputePhysicalResetIpmi

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalFwUpgrade

Fault Code: F1000367

Message

[FSM:FAILED]: sam:dme:ComputePhysicalFwUpgrade

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000367

mibFaultName: fsmFailComputePhysicalFwUpgrade

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputeRackUnitAdapterReset

Fault Code: F1000368

Message

[FSM:FAILED]: sam:dme:ComputeRackUnitAdapterReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000368

mibFaultName: fsmFailComputeRackUnitAdapterReset

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmFailPortPIoInCompatSfpReplaced

Fault Code: F1000398

Message

[FSM:FAILED]: sam:dme:PortPIoInCompatSfpReplaced

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000398

mibFaultName: fsmFailPortPIoInCompatSfpReplaced

moClass: port:PIo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]

Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fsmFailExtpolEpRegisterFsm

Fault Code: F1000399

Message

[FSM:FAILED]: sam:dme:ExtpolEpRegisterFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000399

mibFaultName: fsmFailExtpolEpRegisterFsm

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmFailExtpolRegistryCrossDomainConfig

Fault Code: F1000400

Message

[FSM:FAILED]: sam:dme:ExtpolRegistryCrossDomainConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000400

mibFaultName: fsmFailExtpolRegistryCrossDomainConfig

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmFailExtpolRegistryCrossDomainDelete

Fault Code: F1000401

Message

[FSM:FAILED]: sam:dme:ExtpolRegistryCrossDomainDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000401

mibFaultName: fsmFailExtpolRegistryCrossDomainDelete

moClass: extpol:Registry

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg

fsmFailNfsMountInstMount

Fault Code: F1000417

Message

[FSM:FAILED]: sam:dme:NfsMountInstMount

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000417

mibFaultName: fsmFailNfsMountInstMount

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmFailNfsMountInstUnmount

Fault Code: F1000418

Message

[FSM:FAILED]: sam:dme:NfsMountInstUnmount

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000418

mibFaultName: fsmFailNfsMountInstUnmount

moClass: nfs:MountInst

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/nfs-mount-inst-[name]

fsmFailNfsMountDefReportNfsMountSuspend

Fault Code: F1000419

Message

[FSM:FAILED]: sam:dme:NfsMountDefReportNfsMountSuspend

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000419

mibFaultName: fsmFailNfsMountDefReportNfsMountSuspend

moClass: nfs:MountDef

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: nfs-ep/nfs-mount-def-[name]

fsmFailStorageSystemSync

Fault Code: F1000435

Message

[FSM:FAILED]: sam:dme:StorageSystemSync

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000435

mibFaultName: fsmFailStorageSystemSync

moClass: storage:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: storage-ep/system

fsmFailFirmwareSystemDeploy

Fault Code: F1000448

Message

[FSM:FAILED]: sam:dme:FirmwareSystemDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000448

mibFaultName: fsmFailFirmwareSystemDeploy

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmFailFirmwareSystemApplyCatalogPack

Fault Code: F1000449

Message

[FSM:FAILED]: sam:dme:FirmwareSystemApplyCatalogPack

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000449

mibFaultName: fsmFailFirmwareSystemApplyCatalogPack

moClass: firmware:System

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-system

fsmFailComputeServerDiscPolicyResolveScrubPolicy

Fault Code: F1000466

Message

[FSM:FAILED]: sam:dme:ComputeServerDiscPolicyResolveScrubPolicy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000466

mibFaultName: fsmFailComputeServerDiscPolicyResolveScrubPolicy

moClass: compute:ServerDiscPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/server-discovery

fsmFailSwFcSanBorderActivateZoneSet

Fault Code: F1000479

Message

[FSM:FAILED]: sam:dme:SwFcSanBorderActivateZoneSet

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000479

mibFaultName: fsmFailSwFcSanBorderActivateZoneSet

moClass: sw:FcSanBorder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/border-fc

fsmFailExtpolEpRepairCert

Fault Code: F1000486

Message

[FSM:FAILED]: sam:dme:ExtpolEpRepairCert

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000486

mibFaultName: fsmFailExtpolEpRepairCert

moClass: extpol:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol

fsmFailPolicyControlEpOperate

Fault Code: F1000487

Message

[FSM:FAILED]: sam:dme:PolicyControlEpOperate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000487

mibFaultName: fsmFailPolicyControlEpOperate

moClass: policy:ControlEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]

fsmFailPolicyPolicyScopeReleasePolicyFsm

Fault Code: F1000488

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleasePolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000488

mibFaultName: fsmFailPolicyPolicyScopeReleasePolicyFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseOperationFsm

Fault Code: F1000489

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseOperationFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000489

mibFaultName: fsmFailPolicyPolicyScopeReleaseOperationFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseStorageFsm

Fault Code: F1000490

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseStorageFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000490

mibFaultName: fsmFailPolicyPolicyScopeReleaseStorageFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveManyPolicyFsm

Fault Code: F1000491

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyPolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000491

mibFaultName: fsmFailPolicyPolicyScopeResolveManyPolicyFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveManyOperationFsm

Fault Code: F1000492

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyOperationFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000492

mibFaultName: fsmFailPolicyPolicyScopeResolveManyOperationFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveManyStorageFsm

Fault Code: F1000493

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyStorageFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000493

mibFaultName: fsmFailPolicyPolicyScopeResolveManyStorageFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseManyPolicyFsm

Fault Code: F1000494

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyPolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000494

mibFaultName: fsmFailPolicyPolicyScopeReleaseManyPolicyFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseManyOperationFsm

Fault Code: F1000495

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyOperationFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000495

mibFaultName: fsmFailPolicyPolicyScopeReleaseManyOperationFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseManyStorageFsm

Fault Code: F1000496

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyStorageFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000496

mibFaultName: fsmFailPolicyPolicyScopeReleaseManyStorageFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveAllPolicyFsm

Fault Code: F1000497

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllPolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000497

mibFaultName: fsmFailPolicyPolicyScopeResolveAllPolicyFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveAllOperationFsm

Fault Code: F1000498

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllOperationFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000498

mibFaultName: fsmFailPolicyPolicyScopeResolveAllOperationFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeResolveAllStorageFsm

Fault Code: F1000499

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllStorageFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000499

mibFaultName: fsmFailPolicyPolicyScopeResolveAllStorageFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseAllPolicyFsm

Fault Code: F1000500

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllPolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000500

mibFaultName: fsmFailPolicyPolicyScopeReleaseAllPolicyFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseAllOperationFsm

Fault Code: F1000501

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllOperationFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000501

mibFaultName: fsmFailPolicyPolicyScopeReleaseAllOperationFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailPolicyPolicyScopeReleaseAllStorageFsm

Fault Code: F1000502

Message

[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllStorageFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000502

mibFaultName: fsmFailPolicyPolicyScopeReleaseAllStorageFsm

moClass: policy:PolicyScope

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/controllers/contro-[id]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/providers/prov-[type]/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: extpol/reg/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

Affected MO: policy-ep/scope-cont-[appType]/context-[name]/scope-[policyType]-[resolveType]-[policyName]

fsmFailMgmtExportPolicyReportConfigCopy

Fault Code: F1000524

Message

[FSM:FAILED]: sam:dme:MgmtExportPolicyReportConfigCopy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000524

mibFaultName: fsmFailMgmtExportPolicyReportConfigCopy

moClass: mgmt:ExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/cfg-exp-policy-[name]

Affected MO: org-[name]/db-backup-policy-[name]

fsmFailExtpolProviderReportConfigImport

Fault Code: F1000525

Message

[FSM:FAILED]: sam:dme:ExtpolProviderReportConfigImport

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000525

mibFaultName: fsmFailExtpolProviderReportConfigImport

moClass: extpol:Provider

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]

fsmFailObserveObservedResolvePolicyFsm

Fault Code: F1000531

Message

[FSM:FAILED]: sam:dme:ObserveObservedResolvePolicyFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000531

mibFaultName: fsmFailObserveObservedResolvePolicyFsm

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmFailObserveObservedResolveResourceFsm

Fault Code: F1000532

Message

[FSM:FAILED]: sam:dme:ObserveObservedResolveResourceFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000532

mibFaultName: fsmFailObserveObservedResolveResourceFsm

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmFailObserveObservedResolveVMFsm

Fault Code: F1000533

Message

[FSM:FAILED]: sam:dme:ObserveObservedResolveVMFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000533

mibFaultName: fsmFailObserveObservedResolveVMFsm

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmFailObserveObservedResolveControllerFsm

Fault Code: F1000534

Message

[FSM:FAILED]: sam:dme:ObserveObservedResolveControllerFsm

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000534

mibFaultName: fsmFailObserveObservedResolveControllerFsm

moClass: observe:Observed

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/clients/client-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/controllers/contro-[id]/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/observed-[dataSrcSysId]-[id]

Affected MO: extpol/reg/providers/prov-[type]/observed-[dataSrcSysId]-[id]

Affected MO: observe/observed-[dataSrcSysId]-[id]

fsmFailMgmtControllerRegistryConfig

Fault Code: F1000539

Message

[FSM:FAILED]: sam:dme:MgmtControllerRegistryConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000539

mibFaultName: fsmFailMgmtControllerRegistryConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailGmetaHolderInventory

Fault Code: F1000648

Message

[FSM:FAILED]: sam:dme:GmetaHolderInventory

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000648

mibFaultName: fsmFailGmetaHolderInventory

moClass: gmeta:Holder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: gmeta/category-[category]-provider-[provider]

fsmFailComputePhysicalCimcSessionDelete

Fault Code: F1000649

Message

[FSM:FAILED]: sam:dme:ComputePhysicalCimcSessionDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000649

mibFaultName: fsmFailComputePhysicalCimcSessionDelete

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailPolicyControlledTypeOperate

Fault Code: F1000652

Message

[FSM:FAILED]: sam:dme:PolicyControlledTypeOperate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000652

mibFaultName: fsmFailPolicyControlledTypeOperate

moClass: policy:ControlledType

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/control-ep-[type]/cfg-backup-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/comm-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/datetime-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/discovery-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/dns-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fabric-fw-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/fault-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/mep-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/monitoring-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/powermgmt-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/psu-ctrl/ctrlled-type-[type]

Affected MO: sys/control-ep-[type]/security-ctrl/ctrlled-type-[type]

fsmFailFabricVnetEpSyncEpPushVnetEpDeletion

Fault Code: F1000659

Message

[FSM:FAILED]: sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000659

mibFaultName: fsmFailFabricVnetEpSyncEpPushVnetEpDeletion

moClass: fabric:VnetEpSyncEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: extpol/reg/providers/prov-[type]/syncEp

fsmFailSwEthLanFlowMonDeploy

Fault Code: F1000679

Message

[FSM:FAILED]: sam:dme:SwEthLanFlowMonDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000679

mibFaultName: fsmFailSwEthLanFlowMonDeploy

moClass: sw:EthLanFlowMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ethlanflowmon

fsmFailMgmtIPv6IfAddrSwMgmtOobIpv6IfConfig

Fault Code: F1000705

Message

[FSM:FAILED]: sam:dme:MgmtIPv6IfAddrSwMgmtOobIpv6IfConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000705

mibFaultName: fsmFailMgmtIPv6IfAddrSwMgmtOobIpv6IfConfig

moClass: mgmt:IPv6IfAddr

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/rack-unit-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/ifConfig-ipv6/if-ipv6

Affected MO: sys/switch-[id]/mgmt/if-[id]/ifConfig-ipv6/if-ipv6

fsmFailComputePhysicalUpdateBoardController

Fault Code: F1000707

Message

[FSM:FAILED]: sam:dme:ComputePhysicalUpdateBoardController

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000707

mibFaultName: fsmFailComputePhysicalUpdateBoardController

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailExtvmmNetworkSetsDeploy

Fault Code: F1000743

Message

[FSM:FAILED]: sam:dme:ExtvmmNetworkSetsDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000743

mibFaultName: fsmFailExtvmmNetworkSetsDeploy

moClass: extvmm:NetworkSets

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: fabric/lan/network-sets

fsmFailComputePhysicalConfigBoard

Fault Code: F1000747

Message

[FSM:FAILED]: sam:dme:ComputePhysicalConfigBoard

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000747

mibFaultName: fsmFailComputePhysicalConfigBoard

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalResetMemoryErrors

Fault Code: F1000748

Message

[FSM:FAILED]: sam:dme:ComputePhysicalResetMemoryErrors

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000748

mibFaultName: fsmFailComputePhysicalResetMemoryErrors

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailMgmtControllerExtMgmtInterfaceConfig

Fault Code: F1000754

Message

[FSM:FAILED]: sam:dme:MgmtControllerExtMgmtInterfaceConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000754

mibFaultName: fsmFailMgmtControllerExtMgmtInterfaceConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailComputeRackUnitCreateDhcpEntry

Fault Code: F1000755

Message

[FSM:FAILED]: sam:dme:ComputeRackUnitCreateDhcpEntry

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000755

mibFaultName: fsmFailComputeRackUnitCreateDhcpEntry

moClass: compute:RackUnit

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalServiceInfraDeploy

Fault Code: F1000756

Message

[FSM:FAILED]: sam:dme:ComputePhysicalServiceInfraDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000756

mibFaultName: fsmFailComputePhysicalServiceInfraDeploy

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailComputePhysicalServiceInfraWithdraw

Fault Code: F1000757

Message

[FSM:FAILED]: sam:dme:ComputePhysicalServiceInfraWithdraw

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000757

mibFaultName: fsmFailComputePhysicalServiceInfraWithdraw

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailEquipmentIOCardBaseFePresence

Fault Code: F1000848

Message

[FSM:FAILED]: sam:dme:EquipmentIOCardBaseFePresence

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000848

mibFaultName: fsmFailEquipmentIOCardBaseFePresence

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmFailEquipmentIOCardBaseFeConn

Fault Code: F1000849

Message

[FSM:FAILED]: sam:dme:EquipmentIOCardBaseFeConn

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000849

mibFaultName: fsmFailEquipmentIOCardBaseFeConn

moClass: equipment:IOCardBase

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/slot-[id]

Affected MO: sys/chassis-[id]/sw-slot-[id]

Affected MO: sys/fex-[id]/slot-[id]

fsmFailMgmtControllerLockConfig

Fault Code: F1000853

Message

[FSM:FAILED]: sam:dme:MgmtControllerLockConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000853

mibFaultName: fsmFailMgmtControllerLockConfig

moClass: mgmt:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt

Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt

Affected MO: sys/chassis-[id]/slot-[id]/mgmt

Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt

Affected MO: sys/fex-[id]/mgmt

Affected MO: sys/fex-[id]/slot-[id]/mgmt

Affected MO: sys/mgmt

Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt

Affected MO: sys/rack-unit-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt

Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt

Affected MO: sys/rack-unit-[id]/mgmt

Affected MO: sys/switch-[id]/mgmt

fsmFailSdAppInstanceInstallApplication

Fault Code: F1000859

Message

[FSM:FAILED]: sam:dme:SdAppInstanceInstallApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000859

mibFaultName: fsmFailSdAppInstanceInstallApplication

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmFailSysdebugLogExportPolicyConfigure

Fault Code: F1000870

Message

[FSM:FAILED]: sam:dme:SysdebugLogExportPolicyConfigure

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000870

mibFaultName: fsmFailSysdebugLogExportPolicyConfigure

moClass: sysdebug:LogExportPolicy

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/sysdebug/log-export-policy

fsmFailComputePhysicalFlashController

Fault Code: F1000879

Message

[FSM:FAILED]: sam:dme:ComputePhysicalFlashController

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000879

mibFaultName: fsmFailComputePhysicalFlashController

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailOsControllerDeployOS

Fault Code: F1000903

Message

[FSM:FAILED]: sam:dme:OsControllerDeployOS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000903

mibFaultName: fsmFailOsControllerDeployOS

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmFailNhTableHolderConfigureLinks

Fault Code: F1000906

Message

[FSM:FAILED]: sam:dme:NhTableHolderConfigureLinks

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000906

mibFaultName: fsmFailNhTableHolderConfigureLinks

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmFailStorageFlexFlashControllerMOpsReset

Fault Code: F1000912

Message

[FSM:FAILED]: sam:dme:StorageFlexFlashControllerMOpsReset

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000912

mibFaultName: fsmFailStorageFlexFlashControllerMOpsReset

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmFailStorageFlexFlashControllerMOpsFormat

Fault Code: F1000913

Message

[FSM:FAILED]: sam:dme:StorageFlexFlashControllerMOpsFormat

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000913

mibFaultName: fsmFailStorageFlexFlashControllerMOpsFormat

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmFailStorageFlexFlashControllerMOpsPair

Fault Code: F1000914

Message

[FSM:FAILED]: sam:dme:StorageFlexFlashControllerMOpsPair

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000914

mibFaultName: fsmFailStorageFlexFlashControllerMOpsPair

moClass: storage:FlexFlashController

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-flexflash-[id]

Affected MO: sys/rack-unit-[id]/board/storage-flexflash-[id]

fsmFailIdentMetaSystemUcscUnivSync

Fault Code: F1000917

Message

[FSM:FAILED]: sam:dme:IdentMetaSystemUcscUnivSync

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000917

mibFaultName: fsmFailIdentMetaSystemUcscUnivSync

moClass: ident:MetaSystem

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: metaverse/metasys

fsmFailComputePhysicalEnableCimcSecureBoot

Fault Code: F1000937

Message

[FSM:FAILED]: sam:dme:ComputePhysicalEnableCimcSecureBoot

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000937

mibFaultName: fsmFailComputePhysicalEnableCimcSecureBoot

moClass: compute:Physical

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]

Affected MO: sys/rack-unit-[id]

fsmFailSdAppInstanceStartApplication

Fault Code: F1000951

Message

[FSM:FAILED]: sam:dme:SdAppInstanceStartApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000951

mibFaultName: fsmFailSdAppInstanceStartApplication

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmFailSdLduProvisionLDU

Fault Code: F1000952

Message

[FSM:FAILED]: sam:dme:SdLduProvisionLDU

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000952

mibFaultName: fsmFailSdLduProvisionLDU

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmFailSwExtUtilityConfPortBreakout

Fault Code: F1000957

Message

[FSM:FAILED]: sam:dme:SwExtUtilityConfPortBreakout

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000957

mibFaultName: fsmFailSwExtUtilityConfPortBreakout

moClass: sw:ExtUtility

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ext

fsmFailNhTableHolderBootstrapLinks

Fault Code: F1000960

Message

[FSM:FAILED]: sam:dme:NhTableHolderBootstrapLinks

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000960

mibFaultName: fsmFailNhTableHolderBootstrapLinks

moClass: nh:TableHolder

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/tbh

fsmFailLicenseSmartConfigSetConfig

Fault Code: F1000962

Message

[FSM:FAILED]: sam:dme:LicenseSmartConfigSetConfig

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000962

mibFaultName: fsmFailLicenseSmartConfigSetConfig

moClass: license:SmartConfig

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/license/license-config-[operation]

fsmFailApplicationDownloaderDownload

Fault Code: F1000968

Message

[FSM:FAILED]: sam:dme:ApplicationDownloaderDownload

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000968

mibFaultName: fsmFailApplicationDownloaderDownload

moClass: application:Downloader

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/app-catalogue/dnld-[fileName]

fsmFailSmAppDelete

Fault Code: F1000988

Message

[FSM:FAILED]: sam:dme:SmAppDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000988

mibFaultName: fsmFailSmAppDelete

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmFailSmSecSvcRestoreApplication

Fault Code: F1000989

Message

[FSM:FAILED]: sam:dme:SmSecSvcRestoreApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1000989

mibFaultName: fsmFailSmSecSvcRestoreApplication

moClass: sm:SecSvc

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc

fsmFailOsControllerUpgradeOS

Fault Code: F1001004

Message

[FSM:FAILED]: sam:dme:OsControllerUpgradeOS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001004

mibFaultName: fsmFailOsControllerUpgradeOS

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmFailOsControllerInitOS

Fault Code: F1001005

Message

[FSM:FAILED]: sam:dme:OsControllerInitOS

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001005

mibFaultName: fsmFailOsControllerInitOS

moClass: os:Controller

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl

Affected MO: sys/os-ctrl

Affected MO: sys/rack-unit-[id]/os-ctrl

fsmFailSdAppInstanceUpgradeApplication

Fault Code: F1001006

Message

[FSM:FAILED]: sam:dme:SdAppInstanceUpgradeApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001006

mibFaultName: fsmFailSdAppInstanceUpgradeApplication

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmFailSdAppInstanceStopApplication

Fault Code: F1001007

Message

[FSM:FAILED]: sam:dme:SdAppInstanceStopApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001007

mibFaultName: fsmFailSdAppInstanceStopApplication

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmFailSdAppInstanceUninstallApplication

Fault Code: F1001008

Message

[FSM:FAILED]: sam:dme:SdAppInstanceUninstallApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001008

mibFaultName: fsmFailSdAppInstanceUninstallApplication

moClass: sd:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]

fsmFailSdSlotChangePlatformLogLevel

Fault Code: F1001009

Message

[FSM:FAILED]: sam:dme:SdSlotChangePlatformLogLevel

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001009

mibFaultName: fsmFailSdSlotChangePlatformLogLevel

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmFailSdLogicalDeviceConfigureLinks

Fault Code: F1001011

Message

[FSM:FAILED]: sam:dme:SdLogicalDeviceConfigureLinks

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001011

mibFaultName: fsmFailSdLogicalDeviceConfigureLinks

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmFailSdSlotFormatDisk

Fault Code: F1001014

Message

[FSM:FAILED]: sam:dme:SdSlotFormatDisk

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001014

mibFaultName: fsmFailSdSlotFormatDisk

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmFailSdSlotSynchTimeZone

Fault Code: F1001015

Message

[FSM:FAILED]: sam:dme:SdSlotSynchTimeZone

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001015

mibFaultName: fsmFailSdSlotSynchTimeZone

moClass: sd:Slot

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]

fsmFailSdAppAttributeCtrlGetAppAttributes

Fault Code: F1001016

Message

[FSM:FAILED]: sam:dme:SdAppAttributeCtrlGetAppAttributes

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001016

mibFaultName: fsmFailSdAppAttributeCtrlGetAppAttributes

moClass: sd:AppAttributeCtrl

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-attribute-ctrl

fsmFailSdMgmtInfoUpdateMgmtInfo

Fault Code: F1001017

Message

[FSM:FAILED]: sam:dme:SdMgmtInfoUpdateMgmtInfo

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001017

mibFaultName: fsmFailSdMgmtInfoUpdateMgmtInfo

moClass: sd:MgmtInfo

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/mgmt-info

fsmFailSdNetMgmtBootstrapUpdateNetMgmtBootstrap

Fault Code: F1001018

Message

[FSM:FAILED]: sam:dme:SdNetMgmtBootstrapUpdateNetMgmtBootstrap

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001018

mibFaultName: fsmFailSdNetMgmtBootstrapUpdateNetMgmtBootstrap

moClass: sd:NetMgmtBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/net-mgmt-bootstrap

fsmFailFirmwarePlatformPackPlatformVersion

Fault Code: F1001024

Message

[FSM:FAILED]: sam:dme:FirmwarePlatformPackPlatformVersion

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001024

mibFaultName: fsmFailFirmwarePlatformPackPlatformVersion

moClass: firmware:PlatformPack

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: org-[name]/fw-platform-pack-[name]

fsmFailSwSspEthMonDeploy

Fault Code: F1001040

Message

[FSM:FAILED]: sam:dme:SwSspEthMonDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001040

mibFaultName: fsmFailSwSspEthMonDeploy

moClass: sw:SspEthMon

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]

fsmFailSdClusterBootstrapUpdateClusterConfiguration

Fault Code: F1001043

Message

[FSM:FAILED]: sam:dme:SdClusterBootstrapUpdateClusterConfiguration

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001043

mibFaultName: fsmFailSdClusterBootstrapUpdateClusterConfiguration

moClass: sd:ClusterBootstrap

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/cluster-bootstrap

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/cluster-bootstrap

fsmFailSmAppUpdateApplication

Fault Code: F1001046

Message

[FSM:FAILED]: sam:dme:SmAppUpdateApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001046

mibFaultName: fsmFailSmAppUpdateApplication

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmFailSmAppInstanceResetApplication

Fault Code: F1001047

Message

[FSM:FAILED]: sam:dme:SmAppInstanceResetApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001047

mibFaultName: fsmFailSmAppInstanceResetApplication

moClass: sm:AppInstance

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/slot-[slotId]/app-inst-[appName]

fsmFailIpsecEpUpdateEp

Fault Code: F1001060

Message

[FSM:FAILED]: sam:dme:IpsecEpUpdateEp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001060

mibFaultName: fsmFailIpsecEpUpdateEp

moClass: ipsec:Ep

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/ipsec-ext

fsmFailEtherFtwPortPairConfigFtw

Fault Code: F1001063

Message

[FSM:FAILED]: sam:dme:EtherFtwPortPairConfigFtw

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001063

mibFaultName: fsmFailEtherFtwPortPairConfigFtw

moClass: ether:FtwPortPair

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/fail-to-wire/ftw-port-[slotId]-[aggrPortId]-[portId]-port-[peerSlotId]-[peerAggrPortId]-[peerPortId]

fsmFailSdLinkUpdateInterfaceStatus

Fault Code: F1001064

Message

[FSM:FAILED]: sam:dme:SdLinkUpdateInterfaceStatus

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001064

mibFaultName: fsmFailSdLinkUpdateInterfaceStatus

moClass: sd:Link

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/app-ldulink-[name]-[endpoint1AppInstId]-[endpoint2AppInstId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]/ext-ldulink-[name]-[appInstId]

fsmFailSdUpgradeTaskStopUpgradeStartApp

Fault Code: F1001065

Message

[FSM:FAILED]: sam:dme:SdUpgradeTaskStopUpgradeStartApp

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001065

mibFaultName: fsmFailSdUpgradeTaskStopUpgradeStartApp

moClass: sd:UpgradeTask

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/upgrade-task

fsmFailSwSspEthMonSrcPhyEpDelete

Fault Code: F1001074

Message

[FSM:FAILED]: sam:dme:SwSspEthMonSrcPhyEpDelete

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001074

mibFaultName: fsmFailSwSspEthMonSrcPhyEpDelete

moClass: sw:SspEthMonSrcPhyEp

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/ssp-mon-src-phy-[chassisId]-slot-[slotId]-port-[portId]-aggr-[aggrPortId]

fsmFailFirmwareSupFirmwareDeploy

Fault Code: F1001075

Message

[FSM:FAILED]: sam:dme:FirmwareSupFirmwareDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001075

mibFaultName: fsmFailFirmwareSupFirmwareDeploy

moClass: firmware:SupFirmware

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-supfirmware

fsmFailEquipmentChassisShutdownChassis

Fault Code: F1001083

Message

[FSM:FAILED]: sam:dme:EquipmentChassisShutdownChassis

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001083

mibFaultName: fsmFailEquipmentChassisShutdownChassis

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailSmCloudConnectorRegisterCloudConnector

Fault Code: F1001091

Message

[FSM:FAILED]: sam:dme:SmCloudConnectorRegisterCloudConnector

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001091

mibFaultName: fsmFailSmCloudConnectorRegisterCloudConnector

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmFailSmCloudConnectorUnRegisterCloudConnector

Fault Code: F1001092

Message

[FSM:FAILED]: sam:dme:SmCloudConnectorUnRegisterCloudConnector

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001092

mibFaultName: fsmFailSmCloudConnectorUnRegisterCloudConnector

moClass: sm:CloudConnector

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/cloud-connector

fsmFailSmAppVerifyApplication

Fault Code: F1001093

Message

[FSM:FAILED]: sam:dme:SmAppVerifyApplication

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001093

mibFaultName: fsmFailSmAppVerifyApplication

moClass: sm:App

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/app-[name]-[version]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/app-[name]-[version]

fsmFailSmLogicalDeviceConfigure

Fault Code: F1001096

Message

[FSM:FAILED]: sam:dme:SmLogicalDeviceConfigure

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001096

mibFaultName: fsmFailSmLogicalDeviceConfigure

moClass: sm:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sec-svc/ld-[name]

fsmFailSdLduUpdateInterfaceStatus

Fault Code: F1001098

Message

[FSM:FAILED]: sam:dme:SdLduUpdateInterfaceStatus

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001098

mibFaultName: fsmFailSdLduUpdateInterfaceStatus

moClass: sd:Ldu

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]/ldu-[slotId]

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ldu-[slotId]

fsmFailSdLogicalDeviceConfigureUserMacs

Fault Code: F1001099

Message

[FSM:FAILED]: sam:dme:SdLogicalDeviceConfigureUserMacs

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001099

mibFaultName: fsmFailSdLogicalDeviceConfigureUserMacs

moClass: sd:LogicalDevice

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/ld-[name]

fsmFailEquipmentChassisRebootChassis

Fault Code: F1001100

Message

[FSM:FAILED]: sam:dme:EquipmentChassisRebootChassis

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001100

mibFaultName: fsmFailEquipmentChassisRebootChassis

moClass: equipment:Chassis

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/chassis-[id]

fsmFailFirmwareValidationStatusValidate

Fault Code: F1001104

Message

[FSM:FAILED]: sam:dme:FirmwareValidationStatusValidate

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001104

mibFaultName: fsmFailFirmwareValidationStatusValidate

moClass: firmware:ValidationStatus

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys/fw-catalogue/distrib-[name]/validation

fsmFailSdPortsBundleBundleDataPorts

Fault Code: F1001121

Message

[FSM:FAILED]: sam:dme:SdPortsBundleBundleDataPorts

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001121

mibFaultName: fsmFailSdPortsBundleBundleDataPorts

moClass: sd:PortsBundle

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/ports-bundle

fsmFailSdHotfixInstallHotfix

Fault Code: F1001122

Message

[FSM:FAILED]: sam:dme:SdHotfixInstallHotfix

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001122

mibFaultName: fsmFailSdHotfixInstallHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

fsmFailSdHotfixUninstallHotfix

Fault Code: F1001123

Message

[FSM:FAILED]: sam:dme:SdHotfixUninstallHotfix

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 1001123

mibFaultName: fsmFailSdHotfixUninstallHotfix

moClass: sd:Hotfix

Type: fsm

Callhome: none

Auto Cleared: true

Is Implemented: true

Affected MO: sys-secsvc/slot-[slotId]/app-inst-[appInstId]/hotfix-[hotfixId]

Troubleshooting Transient Faults

Transient faults can occur during initial set up and discovery or when a server or virtual machine starts up. You can typically ignore these transient faults, as FXOS clears them automatically.

This chapter includes the following sections:

- Initial Setup and Discovery Faults

- Virtual Machine Startup Faults

Initial Setup and Discovery Faults

Table 4-1 Transient Faults that Occur during Initial Setup and Discovery Process

Fault Code

Fault Text

Description

F16581

[FSM:STAGE:RETRY:]: user configuration to secondary(FSM-STAGE:sam:dme:

AaaUserEpUpdateUserEp:SetUserPeer)

The FSM could not send the user configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16745

[FSM:STAGE:RETRY:]: QoS Classification Definition classification configuration on secondary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetPeer)

The FSM could not send the quality of the service configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16725

[FSM:STAGE:RETRY:]: VM profile configuration on external VM manager(FSM-STAGE:sam:dme:VnicProfileSetConfigVmm:SetLocal)

The FSM could not send the VM profile configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16580

[FSM:STAGE:RETRY:]: realm configuration to secondary(FSM-STAGE:sam:dme:

AaaRealmUpdateRealm:SetRealmPeer)

The FSM could not send the security configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16724

[FSM:STAGE:RETRY:]: external VM manager configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmEpConfig:SetLocal)

The FSM could not send the VM manager configuration to the primary fabric interconnect during the initial cluster configuration or the setup.

F16579

[FSM:STAGE:RETRY:]: external aaa server configuration to secondary(FSM-STAGE:

sam:dme:AaaEpUpdateEp:SetEpPeer)

The FSM could not send the security configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16749

[FSM:STAGE:RETRY:]: Uplink eth port configuration on B(FSM-STAGE:

sam:dme:SwEthLanBorderDeploy:

UpdateConnectivity)

The FSM could not send the eth-uplink configuration to the fabric interconnects during the initial cluster configuration or the setup.

F16749

[FSM:STAGE:RETRY:]: internal network configuration on B(FSM-STAGE:

sam:dme:SwAccessDomainDeploy:

UpdateConnectivity)

The FSM could not send the internal network configuration to the fabric interconnects during the initial cluster configuration or the setup.

F16749

[FSM:STAGE:RETRY:]: Uplink fc port configuration on B(FSM-STAGE:sam:

dme:SwFcSanBorderDeploy:

UpdateConnectivity)

The FSM could not send the fibre channel uplink configuration to the fabric interconnects during the initial cluster configuration or the setup.

F16680

[FSM:STAGE:RETRY:]: Enable virtual interface on local fabric interconnect

(FSM-STAGE:sam:dme:MgmtIfEnableVip:

Local)

The FSM could not send the virtual interface configuration to the fabric interconnects during the initial cluster configuration or the setup.

F16579

[FSM:STAGE:RETRY:]: keyring configuration on secondary(FSM-STAGE:

sam:dme:PkiEpUpdateEp:SetKeyRingPeer)

The FSM could not send the security configuration to the subordinate fabric interconnect during the initial cluster configuration or the setup.

F16539

[FSM:STAGE:RETRY:]: Fabric interconnect mode configuration to primary(FSM-STAGE:

sam:dme:FabricLanCloudSwitchMode:

SwConfigPeer)

The FSM could not send the end-host mode configuration on to the primary fabric interconnect during the initial cluster configuration or the setup.

F0429

Fabric Interconnect A, HA functionality not ready

The cluster configuration cannot be completed until the chassis discovery is completed.

F0400

Chassis 1 connectivity configuration: un-acknowledged

FXOS discovered the chassis with only one link in the first attempt although the chassis discovery policy is configured for four links. FXOS reacknowledges the chassis to activate the other links.

F0401

IOM 1/2 (B) current connectivity does not match discovery policy: unsupported-connectivity

FXOS discovered the chassis with only one link in the first attempt although the chassis discovery policy is configured for four links.

FXOS can clear this fault when the communication is established between the chassis and the fabric interconnect with that link.

F0440

Chassis discovery policy conflict: Link IOM 1/2/2 to fabric interconnect B:1/1 not configured

FXOS discovered the chassis with only one link in the first attempt although the chassis discovery policy is configured for four links. Until the discovery is successful with that link, the remaining links cannot be marked as active.

FXOS can clear this fault when the communication is established between the chassis and the fabric interconnect with that link.

F0332

AssociatePnuOSLocalDiskConfig fails with Service-Unavailable

During discovery, the server association failed due to an error when configuring the local disk controller.

The associated remote invocation error code is 4106.

F0277

ether port 1 on fabric interconnect B oper state: link-up, reason: FEX not configured

FXOS discovered the chassis with only one link in the first attempt although the chassis discovery policy is configured for four links. Until the discovery is successful with that link, the remaining links cannot be marked as active.

F0276

ether port 4 on fabric interconnect B oper state: link-down, reason: Link failure or not-connected

One or more of the links on the chassis flapped during the initial discovery. This fault is generated when the link is down during the flapping.

F0206

Adapter 1/2/1 is unreachable

During discovery, the adapter information cannot be accessed from the server. This fault clears as soon as the information is available.

F0283

VIF 1 / 2 B-42/44 down, reason: Bound Physical Interface Down

The internal VIF that the FXOS uses during discovery failed.

F0367

No link between IOM port 1/1/2 and fabric interconnect A:1/2

The ethernet server ports flapped on the fabric interconnect during the initial discovery, because the discovery policy was configured for more than one link.

FXOS clears this fault when the initial discovery succeeds with one link and the other links can be marked as active.

F0399

Current connectivity for chassis 1 does not match discovery policy: unsupported-connectivity

FXOS discovered the chassis with only one link in the first attempt although the chassis discovery policy is configured for four links. Until the discovery is successful with that link, the remaining links cannot be marked as active.

F16520

[FSM:STAGE:RETRY:]: Identify pre-boot environment agent on server 1/2

(FSM-STAGE:sam:dme:ComputeBlade

Discover:PnuOSIdent)

The FSM failed to identify the pre-boot environment on the server during discovery.

F77960

[FSM:STAGE:REMOTE-ERROR]: Result: end-point-unavailable Code: unspecified Message: Waiting for BIOS POST Completion information from IBMC(sam:dme:ComputeBladeDiscover:

BiosPostCompletion)

The FSM did not receive a response from the server during discovery and is waiting for the BIOS POST completion information.

F0320

Server 1/1 (service profile: ) has an invalid FRU: mismatch-identity-unestablishable

FXOS could not identify the FRUs from the servers during initial discovery.

F77959

[FSM:STAGE:REMOTE-ERROR]: Result: unidentified-fail Code: ERR-0505-IBMC-fru-retrieval-error Message: Could not get Fru from 7f060101,

dn=fabric/server/chassis-1/slot-1 (sam:dme:FabricComputeSlotEpIdentify:ExecuteLocal)

FXOS could not identify the FRUs from the servers during initial discovery.

F16406

[FSM:STAGE:RETRY:]: triggering chassis discovery via IOM 1/2(right)(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:DiscoverChassis)

In a cluster configuration, after the FXOS discovers the chassis through the I/O module connected to the primary fabric interconnect, it raises discovery through the I/O module connected to the secondary fabric interconnect.

Virtual Machine Startup Faults

When you power on a virtual machine on a server that has network adaptors connected to a distributed virtual wwitch through a port profile, the Events tab of the VMware vCenter may display the following event:

Virtual machine powered On with vNICs connected to dvPorts that have a port level configuration, which might be different from the dvPort group configuration.

If you see this event, you can safely ignore it.

Introduction to System Event Log Messages

This chapter provides general information about System Event Log Messages. The following sections are included:

- Information about System Event Log Messages

- SEL File

- SEL Policy

Information about System Event Log Messages

The system event log (SEL) resides on the CIMC in NVRAM. It records most server-related events, such as over- and under-voltage, temperature events, fan events, events from the BIOS, and so on. It also records platform errors such as memory errors, CPU errors, and so on.

The SEL is mainly used for troubleshooting purposes. FXOS uses SEL records to provide mechanisms for proactive health monitoring of the system (for example, faults and error statistics).

SEL File

The SEL file is approximately 40 KB in size, and no further events are recorded when it is full. It must be cleared before additional events can be recorded.

SEL Policy

The SEL policy can be configured to backup the SEL to a remote server, and, optionally to clear the SEL after a backup operation occurs. A back up operation can be triggered based upon the following actions defined by the user as a part of SEL backup policy.

- On SEL log full

- On change of server association

- On expiration of timer interval, and so on.

You can also manually backup or clear the SEL.

Baseboard Management Controller Messages

The Baseboard Management Controller (BMC) provides the interface to the System Event Log (SEL). The SEL can be accessed from the system side as well as from other external interfaces. The BMC uses a message handler to route messages between the different interfaces. It also monitors and manages the system board, including temperatures and voltages.

The following sections are included:

- SEL Device

- Sensor Data Record Device

- Event Receiver Device

- BMC Commands

- SEL Record Examples

SEL Device

The SEL is a nonvolatile repository for system events. The SEL device is separate from the event receiver device and accepts commands to manage the contents.

This section includes the following topics:

- SEL Event Record Format

- Sensor Initialization Agent

SEL Event Record Format

The SEL messages are logged as a 16 byte string that contains the information about the change that triggered the message.

- Byte 1 and 2 is the record ID.

- Byte 3 is the record type.

- Bytes 4, 5, 6, and 7 is the timestamp

- Bytes 8 and 9 is the generator ID.

- Byte 10 is the version of the event message format.

- Byte 11 is the sensor type.

- Byte 12 is the sensor number.

- Byte 13 is either the event dir (assertion/deassertion event) or the event type.

- Byte 14, 15, and 16 are links to the event data field contents and determines whether the sensor class is about threshold, discrete, or original equipment manufacturer (OEM) settings.

Sensor Initialization Agent

The Sensor Initialization Agent is not a logical device, but a collection of functions and services specific to handling SDR information. The Sensor Initialization Agent works directly with the content of SDRs, in particular, with the sensor data records and the device locator records.

The agent uses the SDR information for sensor and IPMB device initialization during system startup. The agent interprets sensor data records and is directed by the init required fields to load thresholds to sensors that have the threshold initialization required bit set in the SDR records. Other bits in the record direct the agent to enable sensors and devices that come up with sensors, events, or both disabled.

The agent function runs at system power-up and at any system hard resets. We recommend that you run the agent function when the BMC first receives standby power.

In systems that implement power management, the system management software takes additional steps to restore intermediate settings after the system has powered up.

Sensor Data Record Device

The Sensor Data Record (SDR) device provides the interface to the sensor data records. A set of commands store and retrieve sensor data records. The SDR device provides a set of commands for discovering, configuring, and accessing sensors.

This section includes the following topics:

- SDR Repository Interface

- Modal and Nonmodal SDR Repositories

SDR Repository Interface

The SDR repository holds sensor, device locator, and entity association records for all sensors in the platform management subsystem. The BMC provides this interface to the SDR repository. The sensor data records can be accessed by using SDR commands.

Modal and Nonmodal SDR Repositories

There are two SDR repository implementations: modal and nonmodal.

A modal SDR repository is only updated when the controller is in SDR repository update mode. SDR information is kept in nonvolatile storage devices. Lengthy write operations during update can be required, which can interfere with other controller operations. For example, the SDR repository can be stored in a flash device that also holds a portion of the management controller code. A modal SDR repository implementation allows the functions associated with that code to be temporarily unavailable during the update process.

A nonmodal SDR repository can be written to at any time. Writing to the SDR does not impact the operation of other commands in the management controller.

Event Receiver Device

Event messages are special messages sent to management controllers when they detect significant or critical system management events. This includes messages for events such as temperature threshold exceeded, voltage threshold exceeded, power fault, and so on. The device generating an event message notifies the system by sending the message to the event receiver device.

Messages from the event receiver device are directly written into the system event log. The appropriate Add SEL Entry command is sent directly to the SEL device.

BMC Commands

SEL, SDR, and event commands are designed so that the devices that implement those command sets are isolated from the contents of the message. The devices do not interpret the messages. The event receiver device receives and routes event messages. The SEL devices retrieve and store log entries. The SDR devices retrieve and store sensor data records.

This section includes the following topics:

- SEL Device Commands

- SDR Repository Device Commands

- Event Receiver Commands

SEL Device Commands

These are the available SEL device commands:

- Get SEL Info

- Get SEL Allocation Info

- Reserve SEL

- Get SEL Entry

- Add SEL Entry

- Partial Add SEL Entry

- Delete SEL Entry

- Clear SEL

- Get SEL Time

- Set SEL Time

- Get Auxiliary Log Status

- Set Auxiliary Log Status

Get SEL Info

This command returns the number of entries in the SEL, the SEL command version, and the timestamp for the most recent entry and delete or clear.

Get SEL Allocation Info

This command returns the number of possible allocation units, the amount of usable free space (in allocation units), the allocation unit size (in bytes), and the size of the largest contiguous free region (in allocation units). The allocation unit size is the number of bytes in which storage is allocated. For example, if a 16 byte record is to be added, and the SEL has a 32 byte allocation unit size, the record takes up 32 bytes of storage.

Reserve SEL

This command sets the present owner of the SEL, as identified by the software ID or by the requester slave address from the command. The reservation process provides a limited amount of protection at repository access from the Intelligent Platform Management Interface (IPMB) when records are being deleted or incrementally read.

Get SEL Entry

This command retrieves entries from the SEL. The record data field in the response returns the 16 bytes of data from the SEL event record.

Add SEL Entry

This command enables the BIOS to add records to the system event log. Normally, the SEL device and the event receiver service are incorporated into the same management controller. In this case, BIOS or the system SMI handler adds its own events to the SEL by formatting an event message and sending it to the SEL device rather than by using this command.

Partial Add SEL Entry

This command is a version of the Add SEL Entry command. It allows the record to be incrementally added to the SEL. This command must be preceded by a Reserve SEL command. The first partial add must be to offset 0000h, and subsequent partial adds must be done sequentially, with no gaps or overlap between the adds.

Delete SEL Entry

This command deletes the specified entry in the SEL.

Clear SEL

This command erases the SEL contents. This process can take several seconds, based on the type of storage device. The command also shows the status of the erasure.

Get SEL Time

This command returns the time from the SEL device,which uses it for event timestamps.

Set SEL Time

This command initializes the time setting in the SEL device, which uses it for event timestamps.

Get Auxiliary Log Status

This command allows remote software to know whether new information has been added to machine check architecture (MCA) log. The MCA log is a storage area that can be implemented in Intel Itanium-based computer systems and holds information from an MCA handler running from system firmware.

Set Auxiliary Log Status

This command can be used by system software or firmware to set the status returned by the Get Auxiliary Log Status command. Some implementations mght use a private mechanism to set this status, in which case this command can not be provided even if the Get Auxiliary Log Status command is provided.

SDR Repository Device Commands

The following commands control the SDR repository device actions:

- Get SDR Repository Info

- Get SDR Repository Allocation Info

- Reserve SDR Repository

- Get SDR

- Add SDR

- Partial Add SDR

- Delete SDR

- Clear SDR Repository

- Get SDR Repository Time

- Set SDR Repository Time

- Enter SDR Repository Update Mode

- Exit SDR Repository Update Mode

- Run Initialization Agent

Get SDR Repository Info

This command returns the SDR command version for the SDR repository. It also returns a timestamp for the last add, delete, or clear commands.

Get SDR Repository Allocation Info

This command returns the number of possible allocation units, the amount of usable free space (in allocation units), the allocation unit size (in bytes), and the size of the largest contiguous free region (in allocation units). The allocation unit size is the number of bytes in which storage is allocated. For example, if a 20 byte record is to be added, and the SDR repository has a 16 byte allocation unit size, then the record would take up 32 bytes of storage.

Reserve SDR Repository

This command sets the present owner of the repository, as identified by the software ID or the requester slave address from the command. The reservation process provides a limited amount of protection on repository access from the IPMB when records are being deleted or incrementally read.

Get SDR

This command returns the sensor record specified by the record ID. The command also accepts a byte range specification that allows a selected portion of the record to be retrieved (incremental read). The Reserve SDR Repository command must be issued first for an incremental read to an offset other than 0000h. (The Get SDR Repository Info command should be used to verify the version of the SDR repository before sending other SDR repository commands. The command format and operation could change between versions.)

Add SDR

This command adds the specified sensor record to the SDR repository and returns its record ID. The data passed in the request must contain all of the SDR data.

Partial Add SDR

This command is a version of the Add SDR command that allows the record to be incrementally added to the repository. This command must be preceded by a Reserve SDR Repository command. The first partial add must be to offset 0000h, and partial adds must be done sequentially, with no gaps or overlap between the adds.

Delete SDR

This command deletes the sensor record specified by record ID. The requester ID and the reservation ID must also match the owner of the SDR repository.

Clear SDR Repository

This command clears all records from the SDR repository and reinitializes the SDR repository subsystem. The requestor ID and reservation ID information must match the present owner of the SDR repository. We recommend that this command not be used within your utilities and system management software.

Get SDR Repository Time

This command returns the time setting from the SDR repository device, which the SDR repository devices uses for tracking when changes to the SDR repository are made.

Set SDR Repository Time

This command initializes the time setting in the SDR repository device, which the SDR repository devices uses for tracking when changes to the SDR repository are made.

Enter SDR Repository Update Mode

This command enters a mode that allows a subset of normal commands. Available commands are Get Device ID, Get SDR, Add SDR, Partial Add SDR and Clear SDR Repository.

Exit SDR Repository Update Mode

This command exits the SDR repository update mode and restores normal use of all commands.

Run Initialization Agent

This command runs the initialization agent and can also check the status of the agent.

Event Receiver Commands

The following commands can be executed on the event receiver device:

- Set Event Receiver

- Get Event Receiver

- Platform Event Message

Set Event Receiver

This is a global command to tell a controller where to send event messages. The slave address and LUN of the event receiver must be provided. A value FFh for the event receiver slave address disables the generation of event messages.

Get Event Receiver

This is a global command to retrieve the present setting for the event receiver slave address and LUN.

Platform Event Message

This command is a request for the BMC to process event data that the command contains. The data is logged to the SEL.

SEL Record Examples

Examples that are reported to the SEL Repository are provided here. The raw record contains 16 bytes and are dislayed in the examples as hexadecimal values. Following the arrow is the translation of the data. The |-pipes are separators for ease of reading the translation.

The following topics are included:

- Device Presence Changes

- LED Color Changes

- Voltage Changes

- Temperature Changes

Device Presence Changes

These are examples of presence assertions. This shows a boot-up process.

54 01 02 3c 0c 00 00 01 00 04 12 83 6f 01 ff 00 ------------> 154 | 01/01/1970 00:52:12 | BIOS | System Event #0x83 | OEM System Boot Event | | Asserted

55 01 02 3d 0c 00 00 20 00 04 25 53 08 01 ff ff ------------> 155 | 01/01/1970 00:52:13 | BMC | Entity presence BIOS_POST_CMPLT #0x53 | Device Present | Asserted

56 01 02 54 0c 00 00 20 00 04 25 52 08 00 ff ff ------------> 156 | 01/01/1970 00:52:36 | BMC | Entity presence MAIN_POWER #0x52 | Device Absent | Asserted

57 01 02 25 00 00 00 20 00 04 25 41 08 01 ff ff ------------> 157 | 01/01/1970 00:00:37 | BMC | Entity presence MEZZ_PRS #0x41 | Device Present | Asserted

58 01 02 25 00 00 00 20 00 04 25 43 08 00 ff ff ------------> 158 | 01/01/1970 00:00:37 | BMC | Entity presence HDD1_PRS #0x43 | Device Absent | Asserted

59 01 02 25 00 00 00 20 00 04 25 45 08 01 ff ff ------------> 159 | 01/01/1970 00:00:37 | BMC | Entity presence P1_PRESENT #0x45 | Device Present | Asserted

5a 01 02 25 00 00 00 20 00 04 25 47 08 00 ff ff ------------> 15a | 01/01/1970 00:00:37 | BMC | Entity presence DDR3_P2_D2_PRS #0x47 | Device Absent | Asserted

5b 01 02 25 00 00 00 20 00 04 25 49 08 00 ff ff ------------> 15b | 01/01/1970 00:00:37 | BMC | Entity presence DDR3_P2_E2_PRS #0x49 | Device Absent | Asserted

5c 01 02 25 00 00 00 20 00 04 25 4b 08 00 ff ff ------------> 15c | 01/01/1970 00:00:37 | BMC | Entity presence DDR3_P2_F2_PRS #0x4b | Device Absent | Asserted

5d 01 02 26 00 00 00 20 00 04 25 4d 08 00 ff ff ------------> 15d | 01/01/1970 00:00:38 | BMC | Entity presence DDR3_P1_A2_PRS #0x4d | Device Absent | Asserted

5e 01 02 26 00 00 00 20 00 04 25 4f 08 00 ff ff ------------> 15e | 01/01/1970 00:00:38 | BMC | Entity presence DDR3_P1_B2_PRS #0x4f | Device Absent | Asserted

5f 01 02 26 00 00 00 20 00 04 25 51 08 00 ff ff ------------> 15f | 01/01/1970 00:00:38 | BMC | Entity presence DDR3_P1_C2_PRS #0x51 | Device Absent | Asserted

60 01 02 26 00 00 00 20 00 04 25 53 08 01 ff ff ------------> 160 | 01/01/1970 00:00:38 | BMC | Entity presence BIOS_POST_CMPLT #0x53 | Device Present | Asserted

LED Color Changes

These are examples of LED color changes written into the SEL Repository.

34 05 02 2f 00 00 00 20 00 04 24 56 7f 00 04 10 ------------> 534 | 01/01/1970 00:00:47 | BMC | Platform alert LED_MEZZ_TP_FLT #0x56 | LED is off | Asserted

35 05 02 30 00 00 00 20 00 04 24 56 7f 07 04 10 ------------> 535 | 01/01/1970 00:00:48 | BMC | Platform alert LED_MEZZ_TP_FLT #0x56 | LED color is red | Asserted

36 05 02 30 00 00 00 20 00 04 24 58 7f 00 04 10 ------------> 536 | 01/01/1970 00:00:48 | BMC | Platform alert LED_SYS_ACT #0x58 | LED is off | Asserted

37 05 02 31 00 00 00 20 00 04 24 58 7f 04 04 10 ------------> 537 | 01/01/1970 00:00:49 | BMC | Platform alert LED_SYS_ACT #0x58 | LED color is green | Asserted

38 05 02 31 00 00 00 20 00 04 24 5a 7f 00 04 10 ------------> 538 | 01/01/1970 00:00:49 | BMC | Platform alert LED_SAS1_FAULT #0x5a | LED is off | Asserted

39 05 02 32 00 00 00 20 00 04 24 5a 7f 05 04 10 ------------> 539 | 01/01/1970 00:00:50 | BMC | Platform alert LED_SAS1_FAULT #0x5a | LED color is amber | Asserted

Voltage Changes

These are examples of SEL messages when voltage thresholds are crossed.

7b 09 02 3d 19 00 00 20 00 04 02 00 01 52 b5 b7 ------------> 97b | 01/01/1970 01:47:41 | BMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Asserted | Reading 2.39 < Threshold 2.42 Volts

8d 09 02 5b 19 00 00 20 00 04 02 00 81 52 bc b7 ------------> 98d | 01/01/1970 01:48:11 | BMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Deasserted | Reading 2.48 > Threshold 2.42 Volts

Temperature Changes

These are examples of SEL messages when temperature thresholds are crossed.

00 02 02 2b 00 00 00 20 00 04 19 18 05 00 ff ff ------------> 200 | 01/01/1970 00:00:43 | BMC | Chip Set IOH_THERMTRIP_N #0x18 | Limit Not Exceeded | Asserted

12 02 02 31 00 00 00 20 00 04 07 19 05 00 ff ff ------------> 212 | 01/01/1970 00:00:49 | BMC | Processor P2_THERMTRIP_N #0x19 | Limit Not Exceeded | Asserted

13 02 02 32 00 00 00 20 00 04 07 1a 05 00 ff ff ------------> 213 | 01/01/1970 00:00:50 | BMC | Processor P1_THERMTRIP_N #0x1a | Limit Not Exceeded | Asserted

Cisco FXOS Faults and Error Messages, 2.2(1)

April 12, 2017

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco FXOS Faults and Error Messages, 2.2(1)

© 2017 Cisco Systems, Inc. All rights reserved.