HP CloudSystem Foundation Betriebsanweisung Seite 171

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 211
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 170
Volume status is mismatched between CloudSystem Console and CloudSystem Portal
Possible cause and recommendationSymptom
The volume status displayed in the CloudSystem Console
refreshes only once per hour with data from the CloudSystem
Portal
1. No action is required. Always refer to the status displayed in the
CloudSystem Portal for the most current volume status. The hourly refresh
will update the status in the CloudSystem Console.
The current volume status that is
displayed in the CloudSystem Portal is
different than the status displayed in the
CloudSystem Console
Renaming or changing the comment section in volumes with an osv-” prefix in the
3PAR storage system causes the volumes to become inoperable
Possible cause and recommendationSymptom
You renamed a volumes with an osv-” prefix or removed its
comment section in the 3PAR storage system
When you create a block storage volume in the CloudSystem Portal or using
the OpenStack Cinder CLI, the names of the volume in the 3PAR storage
system is prefixed with osv-.
Delete the volume and recreate it in the CloudSystem Portal or using the
OpenStack Cinder CLI.
A volume is inoperable and is deleted
when you run the CloudSystem recovery
procedure
Block storage volumes may indefinitely remain in undesired state
Possible cause and recommendationSymptom
Various possible issues in OpenStack Block Storage (Cinder) or
3PAR storage system
Reset the state using the following OpenStack Cinder command from a
Windows or Linux system where the OpenStack CLI package for
CloudSystem is installed:
cinder reset-state <volume name or ID>
If delete is the desired state, follow the preceding command by entering:
cinder force-delete <volume name or ID>
Volume is stuck in an undesired stated
(detaching, deleting, attaching, and so
on) for a period of time
Last iSCSI initiator configured for an ESX host is used for attaching a volume
Possible cause and recommendationSymptom
Interaction between CloudSystem and ESX
Configure only one iSCSI initiator for an ESX host.
You configured more than one hardware
or software iSCSI initiator on an ESX
host, but only the last initiator that was
configured is used when the volume is
attached
Troubleshooting storage 171
Seitenansicht 170
1 2 ... 166 167 168 169 170 171 172 173 174 175 176 ... 210 211

Kommentare zu diesen Handbüchern

Keine Kommentare