Bestimmen des NFVIS-für-UC-Installationsvolumes

Einleitung

In diesem Dokument werden die Schritte beschrieben, die erforderlich sind, um zu bestimmen, auf welchem Volume NFVIS-for-UC derzeit installiert ist.

Problem

Es muss ermittelt werden, auf welchem Volume NFVIS-for-UC derzeit installiert ist.

Lösung

Schritt 1: Führen Sie eine RedFish API-Abfrage für den CIMC des Hosts aus, um zu ermitteln, wie viele virtuelle Laufwerke über https://<CIMC-IP-Adresse>/redfish/v1/Systems/<CIMC-Seriennummer>/Storage/MRAID/Volumes

Beispielausgabe

{
  "@odata.id": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes",
  "@odata.type": "#VolumeCollection.VolumeCollection",
  "@odata.context": "/redfish/v1/$metadata#VolumeCollection.VolumeCollection",
  "Description": "Collection of Volumes for this system",
  "Name": "Volume Collection",
  "Members@odata.count": 4,
  "Members": [
    {
      "@odata.id": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/0"
    },
    {
      "@odata.id": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/1"
    },
    {
      "@odata.id": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/2"
    },
    {
      "@odata.id": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/3"
    }
  ]
} 

Schritt 2: Fragen Sie die API für jedes Volume ab, wobei "Number" die Nummer des in Schritt 1 angezeigten Volumes ist.https://<CIMC IP Address>/redfish/v1/Systems/<CIMC Serial Number>/Storage/MRAID/Volumes/Number

Beispielausgabe von VD-0

... Obmitted Output ...
  "Id": "0",
  "Name": "NA",
  "Encrypted": false,
  "CapacityBytes": 1494996746240,
  "BlockSizeBytes": 512,
  "OptimumIOSizeBytes": 131072,
  "Identifiers": [
    {
      "DurableNameFormat": "UUID",
      "DurableName": "60027e370b077b003179502a9dc8b57a"
    }
  ],
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  },
  "Actions": {
    "#Volume.Initialize": {
      "target": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/0/Actions/Volume.Initialize",
      "InitializeType@Redfish.AllowableValues": [
        "Fast",
        "Slow"
      ]
    },
    "#Volume.CheckConsistency": {
      "target": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/0/Actions/Volume.CheckConsistency"
    },
    "Oem": {
      "#Cisco.StartReconstruction": {
        "target": "/redfish/v1/Systems/SERIALNUMBER/Storage/MRAID/Volumes/0/Actions/Oem/Cisco.StartReconstruction",
        "@odata.type": "#CiscoUCSExtensions.v1_0_0.StartReconstruction",
        "ReconstructionOp@Redfish.AllowableValues": [
          "add",
          "remove",
          "none"
        ]
      }
    }
  },
  "RAIDType": "RAID5",
  "Oem": {
    "Cisco": {
      "VolumeAccessPolicy": "ReadWrite",
      "RequestedWriteCachePolicy": "WriteBack",
      "ConfiguredWriteCachePolicy": "WriteBack",
      "VolumeDriveCachePolicy": "NoChange",
      "VolumeReadAheadPolicy": "ReadAhead",
      "VolumeIoPolicy": "DirectIo",
      "VolumeState": "Optimal",
      "AvailableSizeMiBytes": 0,
      "Bootable": true,
      "FullDiskEncryptionCapable": false
    }
  }
} 

Schritt 3: Aus der Ausgabedatenerfassung wird der DurableName-Wert für jede der UUIDs ermittelt.

"Identifiers": [
    {
      "DurableNameFormat": "UUID",
      "DurableName": "60027e370b077b003179502a9dc8b57a"  <<- This is the UUID you copy
    } 

Schritt 4. SSH oder Konsolenverbindung zum NFVIS-for-UC und Unterstützung ausführen show list-units | Volume-UUID einschließen.

Schritt 5: Das Volume, auf dem NFVIS-for-UC installiert ist, enthält das Gerät sowie Gerätepartitionen.

Beispielausgabe eines Volumes, auf dem NFVIS-for-UC OS installiert ist.

BE7KH2-NFVIS# support show list-units | include 60027e370b077b003179502a9dc8b57a
  dev-disk-by\x2did-scsi\x2d360027e370b077b003179502a9dc8b57a.device                loaded    active   plugged   UCSC-RAID12GP-4G
  dev-disk-by\x2did-scsi\x2d360027e370b077b003179502a9dc8b57a\x2dpart1.device       loaded    active   plugged   UCSC-RAID12GP-4G 1
  dev-disk-by\x2did-scsi\x2d360027e370b077b003179502a9dc8b57a\x2dpart2.device       loaded    active   plugged   UCSC-RAID12GP-4G 2
  dev-disk-by\x2did-scsi\x2d360027e370b077b003179502a9dc8b57a\x2dpart3.device       loaded    active   plugged   UCSC-RAID12GP-4G 3
  dev-disk-by\x2did-wwn\x2d0x60027e370b077b003179502a9dc8b57a.device                loaded    active   plugged   UCSC-RAID12GP-4G
  dev-disk-by\x2did-wwn\x2d0x60027e370b077b003179502a9dc8b57a\x2dpart1.device       loaded    active   plugged   UCSC-RAID12GP-4G 1
  dev-disk-by\x2did-wwn\x2d0x60027e370b077b003179502a9dc8b57a\x2dpart2.device       loaded    active   plugged   UCSC-RAID12GP-4G 2
  dev-disk-by\x2did-wwn\x2d0x60027e370b077b003179502a9dc8b57a\x2dpart3.device       loaded    active   plugged   UCSC-RAID12GP-4G 3 

Beispiel für die Ausgabe eines Volumes, das nicht NFVIS-for-UC OS Install ist.

BE7KH2-NFVIS# support show list-units | include 60027e370b077b0031790987dc596ab8
dev-disk-by\x2did-scsi\x2d360027e370b077b0031790987dc596ab8.device                loaded    active   plugged   UCSC-RAID12GP-4G
dev-disk-by\x2did-wwn\x2d0x60027e370b077b0031790987dc596ab8.device                loaded    active   plugged   UCSC-RAID12GP-4G