×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC Discovery 11.3 ... Developing Node lifecycle Inferred nodes

File System node

A File System node represents a file system mounted on a host. On a host there is a File System node for each discovered local, exported, and remote file system.

Currently File System nodes are not synced to CMDB by the default syncmapping sets. This can be extended.

File System Model Illustration

FileSystem nodes come in the following types:

  • LOCAL — A filesystem that is LOCAL to the device, for instance a directly attached disk drive. SAN storage appears to the OS as LUNs on a SCSI chain filesystem, so these devices are reported as LOCAL.
  • REMOTE — A filesystem that is attached over the network from another device. This is the client side of a network filesystem.
  • EXPORTED — A filesystem (or part of a filesystem) which is available for other devices to use. This is the server side of a network filesystem.

An important aspect of this model is that the REMOTE type is the client's view of an EXPORTED filesystem. If both server and client ends are discovered there is a single EXPORTED FileSystem node attached to the server Host node and multiple REMOTE FileSystem instances, a single instance attached to each client Host node.

Network file systems generally export a fraction of an underlying LOCAL filesystem. Thus, on a server exporting filesystems it is expected that the LOCAL and EXPORTED FileSystems instances will be related by the FileSystem:Local:NetworkFileSystem:Exported:FileSystem relationship showing which LOCAL filesystem supports the EXPORTED filesystem. There might be several EXPORTED FileSystem nodes related to the same LOCAL FileSystem node, for instance on a Windows server the two shares C$ and ADMIN$ will usually both be exported from the same C: local filesystem.

The above diagram shows a client (right side) and server (left side) Host. The server might be a UNIX server exporting a section of a local filesystem via NFS, or a Windows server exporting a shared folder via SMB. For each client mounting the NFS/SMB filesystem, the filesystem will be represented by a REMOTE FileSystem.

It is important to remember this distinction if you are considering synchronizing these nodes to the CMDB. The BMC Discovery model and the Common Data Model (CDM) have very different semantics around "remote" filesystems. Currently it is recommended to simply synchronize these to BMC_FileSystem.

File System Lifecycle

A File System node is related to the host it is contained in. Therefore, the File System node lifecycle is directly tied to the Host node and is destroyed when the Host node is destroyed. See Host node.
This is a Containment Removal type, see Containment Removal.

Additionally if both ends of a network filesystem can be discovered the system builds a NetworkFileSystem relationship between the appropriate REMOTE and EXPORTED FileSystem nodes.

File System node attributes

The attributes of a File System node are as described in the following table:

UI Name
Attribute Name and Type; Target

Description

Key
key string

File system unique identifier.

Name
name string

Meaningful file system name for reporting.

Filesystem Name
fs_name string

File system name.

Kind
fs_kind string

File system kind.

Type
fs_type string

File system type.

Mount
mount string

File system mount.

Size
size int

File system size in KB.

Used
used int

File system used in KB.

Free
free int

File system free in KB.

Used Percentage
used_percentage int

File system used percentage.

Free Percentage
free_percentage int

File system free percentage.

Remote Hostname
remote_hostname string

Hostname of remote server for REMOTE File Systems.

Remote IP Address
remote_ip string

IP Address of remote server for REMOTE File Systems.

Remote Username
remote_username string

Username used to access REMOTE File System.

Remote Name
remote_fs_name string

Remote file system name.

Exported Path
path string

Exported path.

Has Qtrees
has_qtrees boolean

Has related Qtrees.

Is a Qtree
qtree boolean

Is a Qtree.

Owning Volume
root_volume string

Root Volume.

Alternative Filesystem Names
fs_aliases list:string

Aliases for file system name.

File System node relationships

The relationships of a File System node are as described in the following table:

UI Name

Relationship

Description

Host

FileSystem:
MountedFileSystem:
FileSystemMount:
Mounter:
Host

Host with FileSystem.

Storage System

FileSystem:
MountedFileSystem:
FileSystemMount:
Mounter:
StorageSystem

Storage with FileSystem.

Mounted As

FileSystem:
Provider:
StorageUse:
Consumer:
FileSystem

Export to Remote network file system.

Mounted From

FileSystem:
Consumer:
StorageUse:
Provider:
FileSystem

Remote to Exported network file system.

Exported From

FileSystem:
Exported:
ExportedFileSystem:
Local:
FileSystem

Export to Local network file system.

Exported Directories

FileSystem:
Local:
ExportedFileSystem:
Exported:
FileSystem

Local to Exported network file system.

Inference

InferredElement:
Inference:
Primary:
DiscoveredFileSystem

Primary inference.

Storage Volume

FileSystem:
Consumer:
StorageUse:
Provider:
StorageVolume

Volume providing storage.

Disk Drive

FileSystem:
Consumer:
StorageUse:
Provider:
DiskDrive

DiskDrive providing storage.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Duncan Tweed on Jan 18, 2018

Comments

Log in or register to comment.

File node
Functional Component node
© Copyright 2004 - 2022 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.