File system for system log not mounted alarms device N8500 version V100R005C00

Publication Date:  2015-12-01 Views:  316 Downloads:  0
Issue Description

Fault symptom:

The customer reported an alarm regarding the file system for  system log not mounted in the device N8500

Description of the alarm:

Configuration and operation scenario

After this,TAC asked  apply the next commands in the N8500

#gabconfig –a

#cfsmntadm display

#vxdisk list

#cat /opt/HS/conf/version.conf

The ouput of the command was the below:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.10.26 11:31:50 =~=~=~=~=~=~=~=~=~=~=~=
login as: support
Using keyboard-interactive authentication.
Password:
Last login: Mon Oct 26 11:31:25 2015 from 172.29.152.126
***********************************************************
*           S5500T Clustered NAS Storage System           *
*                                                         *
*                   Enterprise Edition                    *
* Warning: Only S5500T Clustered NAS Storage System distributed *
*     patches & RPMs can be installed on this system!     *
*     Do not delete contents of lost+found directory      *
*        of filesystems as it may contain critical        *
* temporary S5500T Clustered NAS Storage System configuration data! *
***********************************************************
[?1034h_01:~ #
_01:~ #
_01:~ # gabconfig .a-a
GAB Port Memberships
===============================================================
Port a gen   267202 membership 01
Port b gen   267204 membership 01
Port f gen   26720e membership 01
Port h gen   267206 membership 01
Port u gen   26720c membership 01
Port v gen   267208 membership 01
Port w gen   26720a membership 01
_01:~ #
_01:~ #
_01:~ # cfsmntadm display
  Cluster Configuration for Node: CONAGUA_01
  MOUNT POINT        TYPE      SHARED VOLUME     DISK GROUP       STATUS
  /vx/Omar         Regular    Omar             sfsdg            MOUNTED      
  /vx/fs-zgama     Regular    fs-zgama         sfsdg            MOUNTED      
  /vx/fs-eceledon  Regular    fs-eceledon      sfsdg            MOUNTED      
  /vx/__LogFS__    Regular    __LogFS__        sfsdg            MOUNTED      
  /vx/WIN_FS_NAS   Regular    WIN_FS_NAS       sfsdg            NOT MOUNTED  
  /var/lib/nfs/sm  Regular    _nlm_            sfsdg            MOUNTED      


  Cluster Configuration for Node: CONAGUA_02
  MOUNT POINT        TYPE      SHARED VOLUME     DISK GROUP       STATUS
  /vx/Omar         Regular    Omar             sfsdg            MOUNTED      
  /vx/fs-zgama     Regular    fs-zgama         sfsdg            MOUNTED      
  /vx/fs-eceledon  Regular    fs-eceledon      sfsdg            MOUNTED      
  /vx/__LogFS__    Regular    __LogFS__        sfsdg            MOUNTED      
  /vx/WIN_FS_NAS   Regular    WIN_FS_NAS       sfsdg            NOT MOUNTED  
  /var/lib/nfs/sm  Regular    _nlm_            sfsdg            MOUNTED      


CONAGUA_01:~ #
CONAGUA_01:~ #
CONAGUA_01:~ # vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
huawei-s5500t0_9 auto:simple     huawei-s5500t0_12  sfscoorddg   online
huawei-s5500t0_10 auto:simple     huawei-s5500t0_10  sfsdg        online shared
huawei-s5500t0_11 auto:simple     huawei-s5500t0_9  sfscoorddg   online
huawei-s5500t0_12 auto:simple     huawei-s5500t0_11  sfscoorddg   online
huawei-s5500t0_16 auto:simple     huawei-s5500t0_16  sfsdg        online shared
_01:~ #
_01:~ #
_01:~ # cat /opt/HS/conf/version.conf
N8000V200R001C00SPC104B011|26774|Sat Jul  6 19:26:15 CST 2013
_01:~ #

With thist ouput  information TAC realized that there is not log file system created and that is the reason of the alarm.

Solution

the filesystem log should be created automatically when the first filesystem is created.

Troubleshooting:

Was founded ahat the file engine N8500 has 2 volumes, one with the size 100GB and into this volume were created 3 filesystem, the other volume with size of 300GB it was empty.

TAC engineer created a filesystem in the volume with 100GB size called "TEST" due to this the filesystem should be created automatically but never happened.

TAC engineer created a new filesystemcalled "TEST2" in the volume with the size 300GB, when the filesystem TEST2 was created, appeared automatically the filesystem log and after that alarm disappeared automatically and the customer reported that everything ws up and running, the issue was solved.

The filesystems creted for test were deleted.

Root cause:

The filesystems were created in the volume with 100GB, RnD confirmed that to be createdthe filesystem log automatically, the volume at least needs to have 200GB, the customer created all the filesystems in the volum with 100GB(less that required) for that reason never was created the filesystem log.

Suggestion:

check first to create a volume that the size needs to be 200GB.

END