check_thecus_nas | Nagios check plugin for Thecus NAS devices | Network Attached Storage library

by mhoogveld PHP Version: v1.0 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | check_thecus_nas Summary

check_thecus_nas is a PHP library typically used in Storage, Network Attached Storage applications. check_thecus_nas has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

This plugin can check the health and status of a Thecus NAS device by querying the Web UI (User Interface) of the NAS. It has been developed and tested against. It can check and report CPU usage, system- and CPU-fans, RAID status, available disk space, disk health (bad-sectors) and disk temperature. The Thecus NAS device has (or at least some have) the option to enable and read out SNMP, but this option gives far less information than what can be seen in (and retrieved from) the management user-interface. This check gets its information from this management user-interface through a series of http-requests which return information in json-format. Basing a check on a user-interface is generally not a good idea because user-interfaces are not guaranteed to be the same between different Thecus models and even firmware versions of the same model. This is however the only way to extract extra information like raid-status, drive temperatures and failures.

Support

Quality

Security

License

Reuse

Support

check_thecus_nas has a low active ecosystem.

It has 2 star(s) with 2 fork(s). There are 2 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 1 have been closed. On average issues are closed in 455 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of check_thecus_nas is v1.0

Quality

check_thecus_nas has 0 bugs and 0 code smells.

Security

check_thecus_nas has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

check_thecus_nas code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

check_thecus_nas is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

check_thecus_nas releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of check_thecus_nas

Get all kandi verified functions for this library.

check_thecus_nas Key Features

No Key Features are available at this moment for check_thecus_nas.

check_thecus_nas Examples and Code Snippets

No Code Snippets are available at this moment for check_thecus_nas.

Community Discussions

Trending Discussions on Network Attached Storage

How can I read/write data from/to network attached storage with kedro?

About NAS and SAN(protocols, architecture, etc..)

QUESTION

How can I read/write data from/to network attached storage with kedro?

Asked 2020-May-14 at 09:24

In the API docs about kedro.io and kedro.contrib.io I could not find info about how to read/write data from/to network attached storage such as e.g. FritzBox NAS.

...

ANSWER

Answered 2020-May-14 at 09:24

So I'm a little rusty on network attached storage, but:

If you can mount your network attached storage onto your OS and access it like a regular folder, then it's just a matter of providing the right filepath when writing the config for a given catalog entry. See for example: Using Python, how can I access a shared folder on windows network?
Otherwise, if accessing the network attached storage requires anything special, you might want to create a custom dataset that uses a Python library for interfacing with your network attached storage. Something like pysmb comes to mind.

The custom dataset could borrow heavily from the logic in existing kedro.io or kedro.extras.datasets datasets, but you replace the filepath/fsspec handling code with pysmb instead.

Source https://stackoverflow.com/questions/61791713

QUESTION

About NAS and SAN(protocols, architecture, etc..)

Asked 2020-Apr-07 at 09:44

I am currently kind of having trouble to understand between NAS and SAN.

As far as I figured out, NAS and SAN are kind of defined as below.

NAS(Network attached storage)
- Usually used as file storage and use Ethernet Infrastructure to communicate
- As file storage, support protocols like NFS, CIFS, SMB, HTTP(S)

SAN(Storage Area Network)
- Network Protocol to communicate with block storage for data access.
- Configured with separated network system
- Commonly based on Fibre Channel(FC) technology.
- Could use iSCSI(in small and medium sized business) or FCoE for less expensive alternative to FC

So, below is my questions.
1. Is File Storage and Block Storage are the solutions? I researched and found that NAS is File Storage Solution and SAN Storage is Block Storage Solution.
- In that case, are their base infrastructure(storage device) same? Only different with protocols, network devices, may be storage os something that controls underline device and way of usage?

2. I found there are NAS Solutions that support iSCSI. But I found that iSCSI is SCSI Protocol that use TCP/IP Network system and SCSI is for block level storage communication protocols.
- And Now I am confused. NAS is a file storage solution and how could that support iSCSI Protocol?

3. Are AWS root disk and EBS storage SAN Storage?
- I read that SAN Storage configuration could be expensive so iSCSI or FCoE are less expensive way to configure.
- With what technology AWS storage Infrastructure is configured??

I am kind of newly studying of these storage part computer science and got some questions.
Is there anyone can explain those questions clearly?
Thank you.

...

ANSWER

Answered 2020-Apr-07 at 09:44

It depends on what you call a "Solution". The basic infrastructure is the same it's a some kind of a "storage server" (storage system) with physical disk(s), but it very much dependent of technologies, vendors and various options. Typically, a storage system provides access to its physical disks with different protocols of 2 main groups: block-level protocols like SCSI or rarely ATA on one hand, or file-level protocols like NFS, CIFS, etc on the other. It doesn't mean, a storage system can't work in both, block and file modes.

Storage network - SAN can be build over FC, FCoE, converged infrastructure, pure TCP/IP for iSCSI, Infiniband or any other infrastructure. Typically, when people say "SAN" they mean Block storage devices and FC protocol, but it doesn't mean, that a file storage - NAS can't be connected with SAN and vice verse.

Source https://stackoverflow.com/questions/60768967

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install check_thecus_nas

Place the check script anywhere you'd like (eg /usr/local/lib/nagios/plugins) and run it.
PHP version 5.3 or 7.x (earlier versions are untested)
php5_curl or php_curl For Debian based systems (e.g. Ubuntu): sudo apt-get install php-curl

Support

If you have a Thecus NAS (or a NAS similar to a Thecus) and this check does not work as expected, the URIs and/or returned JSON might not match what the supported models use. Your model might require calling different URIs or returns the data in a different JSON structure. To see what data is returned in JSON format by the currently configured URIs, run the script with the --debug parameter for each check type (health, cpu, memory and disk-usage). The returned JSON can then be matched against the php code and necessary changes can be made to add support. To see what URIs should be used, in the case that no or not enough information is returned, you can use a webbrowser and log in to your NAS. Use the network monitoring part of the browsers developer tools to see what the Web UI uses by browsing to the pages where this information is displayed. In Firefox use F12, in Chrome use Ctrl-Shift-i. Please feel free to make any improvements to this script and send me a pull request. In case of support for a new model, please create a file with model specific output, like the ones in the model-output directory. These files are base on the output of the check when run with the --debug parameter. If you would like support for a model, but you don't know how to add it, you could try to send me the output as mentioned above and I might be able to add support that way.

Find more information at: