Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2009275.1
Update Date:2015-05-14
Keywords:
Solution Type  Problem Resolution Sure

Solution  2009275.1 :   Oracle ZFS Storage Appliance: Slow BUI login and 'Status' screen Analytics only show very recent data  

Related Items 
    

  • Sun ZFS Storage 7420
    •  
  • Oracle ZFS Storage ZS3-2
    •  
  • Sun Storage 7110 Unified Storage System
    •  
  • Oracle ZFS Storage ZS4-4
    •  
  • Sun ZFS Backup Appliance
    •  
  • Sun Storage 7210 Unified Storage System
    •  
  • Sun Storage 7410 Unified Storage System
    •  
  • Sun ZFS Storage 7120
    •  
  • Oracle ZFS Storage ZS3-4
    •  
  • Sun Storage 7310 Unified Storage System
    •  
  • Sun ZFS Storage 7320
    •  
  • Oracle ZFS Storage ZS3-BA
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
    •  




If required analytics datasets on the ZFS Storage Appliance are deleted from the OS shell, the BUI login will be delayed as these are created in memory and the Status page will show no activity for the removed datasets prior to the BUI login.

In this Document
Symptoms
Changes
Cause
Solution

Created from <SR 3-10669326051>

Applies to:

Oracle ZFS Storage ZS4-4 - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun ZFS Backup Appliance - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

Login to the ZFS Storage Appliance BUI is slow and analytics on the Status screen only show data from the moment of login.

 

Image of the BUI status screen showing the issue.

 

Changes

 Deletion of analytics dataset(s) displayed on the Status screen.

Cause

If any of the analytics datasets displayed in the Status screen are deleted, and not recreated, the ZFS Storage Appliance BUI login will be delayed as these are created in memory and the Status page will show no activity for the removed datasets prior to the BUI login.  Since these are in memory and not stored on disk, once the user logs out of the BUI they are discarded.

 

There are eight analytics datasets that must exist on the ZFS Storage Appliance to avoid this issue as they are displayed on the BUI Status page and reported in the Activity status:

ZFSSA:> status activity show
Activity:
   CPU             0 %util                  Sunny
   FTP             0 bytes/sec              Sunny
   Disk           41 ops/sec                Sunny
   iSCSI           0 ops/sec                Sunny
   NFSv3           0 ops/sec                Sunny
   NFSv4           0 ops/sec                Sunny
   Network        3K bytes/sec              Sunny
   SMB             0 ops/sec                Sunny


These represent :

  •  CPU: percent utilization
  •  Protocol: FTP bytes per second
  •  Disk: I/O operations per second
  •  Protocol: iSCSI operations per second
  •  Protocol: NFSv3 operations per second
  •  Protocol: NFSv4 operations per second
  •  Network: device bytes per second
  •  Protocol: SMB operations per second    


They are seen in the CLI as:

ZFSSA:> analytics datasets show
Datasets:

DATASET     STATE   INCORE ONDISK NAME
dataset-000 active   33.9K      0 cpu.utilization
dataset-001 active   33.9K      0 ftp.kilobytes
dataset-002 active   33.9K      0 io.ops
dataset-003 active   33.9K      0 iscsi.ops
dataset-004 active   33.9K      0 nfs3.ops
dataset-005 active   33.9K      0 nfs4.ops
dataset-006 active   33.9K      0 nic.kilobytes
dataset-007 active   33.9K      0 smb.ops



If these datasets are deleted, the ZFS Storage Appliance BUI login will be delayed as these are created in memory and the Status page will show no activity for the removed datasets prior to the BUI login.

Since these are in memory and not stored on disk, once the user logs out of the BUI they are discarded.

This can be confirmed by viewing the datasets before and after a BUI login and then again after the user is loged out of the BUI.

Some of the required and also non-required datasets may exist, but in this example all have been removed.

ZFSSA:> analytics datasets show

<Some of the aformentioned required datasets will be missing>

Login to the ZFS Storage Appliance BUI and the missing required datasets are created.

ZFSSA:> analytics datasets show
Datasets:

DATASET     STATE   INCORE ONDISK NAME
dataset-000 active   33.9K      0 cpu.utilization
dataset-001 active   33.9K      0 ftp.kilobytes
dataset-002 active   33.9K      0 io.ops
dataset-003 active   33.9K      0 iscsi.ops
dataset-004 active   33.9K      0 nfs3.ops
dataset-005 active   33.9K      0 nfs4.ops
dataset-006 active   33.9K      0 nic.kilobytes
dataset-007 active   33.9K      0 smb.ops


Logout of the ZFS Storage Appliance BUI and they are gone.

ZFSSA:> analytics datasets show

<Some of the required datasets will again be missing>
 

Solution

Recreate the missing analytics datasets.

ZFSSA:> analytics datasets create cpu.utilization
ZFSSA:> analytics datasets create ftp.kilobytes
ZFSSA:> analytics datasets create io.ops
ZFSSA:> analytics datasets create iscsi.ops
ZFSSA:> analytics datasets create nfs3.ops
ZFSSA:> analytics datasets create nfs4.ops
ZFSSA:> analytics datasets create nic.kilobytes
ZFSSA:> analytics datasets create smb.ops

 

Restart the akrc service and the default datasets will be created on disk.

ZFSSA:> confirm shell svcadm restart akrc
ZFSSA:> analytics datasets show
Datasets:

DATASET     STATE   INCORE ONDISK NAME
dataset-000 active   61.7K  32.7K arc.accesses[hit/miss]
dataset-001 active   41.8K  31.2K arc.l2_accesses[hit/miss]
dataset-002 active   41.8K  31.2K arc.l2_size
dataset-003 active   41.8K  31.2K arc.size
dataset-004 active   79.2K  32.7K arc.size[component]
dataset-005 active   41.8K  31.2K cpu.utilization
dataset-006 active   54.0K  32.6K cpu.utilization[mode]
dataset-007 active   56.2K  32.6K dnlc.accesses[hit/miss]
dataset-008 active   41.8K  31.2K fc.bytes
dataset-009 active   41.8K  31.2K fc.ops
dataset-010 active   41.8K  31.2K ftp.kilobytes
dataset-011 active   41.8K  31.2K http.reqs
dataset-012 active   41.8K  31.2K io.bytes
dataset-013 active   49.5K  32.5K io.bytes[op]
dataset-014 active   41.8K  31.2K io.disks[utilization=95][disk]
dataset-015 active   41.8K  31.2K io.ops
dataset-016 active   53.4K  32.5K io.ops[disk]
dataset-017 active   49.4K  32.5K io.ops[op]
dataset-018 active   41.8K  31.2K iscsi.bytes
dataset-019 active   41.8K  31.2K iscsi.ops
dataset-020 active   41.8K  31.2K ndmp.diskkb
dataset-021 active   41.8K  31.2K nfs2.ops
dataset-022 active   41.8K  31.2K nfs2.ops[op]
dataset-023 active   41.8K  31.2K nfs3.ops
dataset-024 active   41.8K  31.2K nfs3.ops[op]
dataset-025 active   41.8K  31.2K nfs4.ops
dataset-026 active   41.8K  31.2K nfs4.ops[op]
dataset-027 active   41.8K  31.2K nic.kilobytes
dataset-028 active   45.6K  31.2K nic.kilobytes[device]
dataset-029 active   46.1K  31.2K nic.kilobytes[direction]
dataset-030 active   41.8K  31.2K sftp.kilobytes
dataset-031 active   41.8K  31.2K smb.ops
dataset-032 active   41.8K  31.2K smb.ops[op]


Attachments 
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback