This documentation supports the 21.05 (12.2) version of BMC Discovery.To view an earlier version of the product, select the version from the Product version menu.

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

fs_design_pattern.png

 

 

 

 

 

 




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:

File System node relationships

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*