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

The following table describes the transient faults that you may see during the initial setup and discovery process. FXOS clears these faults. If you see them during the initial setup or discovery process, you can safely ignore these faults.

Table 1. Transient Faults that Occur during Initial Setup and Discovery Process

Fault Code

Fault Text

Description

F17254

[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.

F17253

[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.

F17252

[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.

F78107

[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.

F78109

[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.

F78933

[FSM:STAGE:RETRY:]: Enable virtual interface on local fabric interconnect

The FSM could not send the virtual interface configuration to the fabric interconnects during the initial cluster configuration or the setup.

F17251

[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.

F17477

[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.

F16520

[FSM:STAGE:RETRY:]: Identify pre-boot environment agent on server 1/2 (FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSIdent)

The FSM failed to identify the pre-boot environment on the server during discovery.

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.