Fenix Web Server | simple static web server

I needed to stage software for an upgrade over the weekend. During the upgrade, you load the new files over HTTP. In the past, I just looked for an available web server I could use to do this. Or, if none existed, I would install IIS or Apache, leave it running until the next time I needed it, and it would become one of those multi-purpose “SAN” servers that’s a http, ftp, monitoring, log gathering, perfstat running, many-headed hydra of a server that’s both really important and not important enough to wake me up at 2am about.

But I am learning..and I started looking for a lightweight web server that’s preferably ad-hoc (stop and start the server only when I needed it), preferably open source, and simple to use; I just want to load my files into a folder and grab those files during an install.

The solution I found is called Fenix: http://fenixwebserver.com/

It’s available for Windows and Mac. It’s open source. As of this post, the project’s currently on version 2.0.0. It’s very simple to use. Out of the box, there is no default web server it creates. You add web servers using an intuitive interface, although there are command-line options should you want to go that route.

I created a folder called HTTP-Root, and placed my system files in there. You give the server a name to identify it, the path, and the port.

You can create mutiple sites side by side. For my purposes I only needed one. From the application window, you start your server.

And that’s all there is to it. I used it for the upgrade and stopped it when I was finished. Worked like a champ. Was just what I was looking for. Definitely recommend.

>software get http://ipaddress/814P9_q_image.zip
software: copying to /etc/software/814P9_q_image.zip  
software: 100% file read from location.  
software: /etc/software/814P9_q_image.zip has been copied.  
>software install 814P9_q_image.zip               
software: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.  
software: Depending on system load, it may take many minutes  
software: to complete this operation. Until it finishes, you will  
software: not be able to use the console.  
software: installing software, this could take a few minutes...  
software: installation of 814P9_q_image.zip completed.  
Sat Aug 27 18:24:25 MDT [: cmds.software.installDone:info]: Software: Installation of 814P9_q_image.zip was completed.  
Please type "download" to load the new software,  
and "reboot" subsequently for the changes to take effect.  
>download

The mount request was denied by the NFS server | VMware | Troubleshooting netgroups

Call “HostDatastoreSystem.CreateNasDatastore” for object “datastoreSystem-663108” on vCenter Server failed.
NFS mount failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.
An unknown error has occurred.

VMware message encountered while trying to mount volume from newly added nodes 13 and 14 in a 14 node cluster running 8.3.2P2.

Troubleshooting steps:

  • Checked namespace export policy – looked good; identical to dozens of other volumes backed by node1 thru node12 already mounted as VMware datastores.
  • Tested mounting on different vSphere hosts – same message.
  • As the export policy uses local netgroups, I checked the local netgroups definitions file:
vserver services name-service netgroup file show  
  • File looked fine.
  • Checked the status of netgroups definitions across all nodes in the cluster – found the culprit:
::> set -privilege advanced

Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.  
Do you want to continue? {y|n}: y

::*> vserver services name-service netgroup status
Vserver   Node            Load Time           Hash Value  
--------- --------------- ------------------- -------------------
vs01  
          node13 
                          -                   -

          node14 
                          -                   -

vserver services name-service netgroup status enables you to verify that netgroup definitions are consistent across all nodes that back a SVM into which netgroup definitions have been loaded.

The command displays the following information:

  • SVM name
  • Node name
  • Load time for netgroup definitions
  • Hash value of the netgroup definitions

Node13 and node14 contained no load time or hash value, as this is a manual step, and doesn’t happen automatically when a node is added. No worries. To resolve, I reloaded the netgroup file onto the SVMs:

::> vserver services name-service netgroup load -vserver vservername -source http://ipaddress/netgroup.txt

This loaded the netgroup file onto node13 and node14, which took about 5 minutes to build the netgroup.byhost map. (I tried mounting on vSphere host immediately after netgroup load, and got the same error message. Waited 5 minutes, and it mounted fine.)

More on displaying the local netgroup definitions status here:
https://library.netapp.com/ecmdocs/ECMP12452955/html/vserver/services/name-service/netgroup/status.html

Check if a datastore is SIOC Enabled | VMware

Researching unmanaged workloads today..here’s a quick way to check if your datastore is managed by Storage I/O Control (SIOC):

Get-Datastore | Select-Object Name, Type, StorageIOControlEnabled  

If you want to check VMhosts for SIOC events, like “An unmanaged I/O workload is detected on a SIOC-enabled datastore”:

Get-VMHost | Get-VIEvent | Where {$_.fullformattedmessage -like '*SIOC*'} | Select FullFormattedMessage, CreatedTime  

VMware Error: “msg.hbacommon.outofspace: There is no more space for virtual disk”

msg.hbacommon.outofspace:There is no more space for virtual disk .vmdk. You may be able to continue this session by freeing disk space on the relevant partition, and clicking Retry. Otherwise, click Abort to terminate this session.

I haven’t seen this message in awhile (knock-on-wood), but if this does occur, you will need to (1) add space to the datastore and (2) answer the message prompt. If this datastore housed a number of VMs, you could have your hands busy clicking VMs and answering message prompts.

Or you could use PowerCLI.

To target all VMs:
Get-VM | Get-VMQuestion | Answer-VMQuestion -DefaultOption  
To target all VMs on a specific datastore:
Get-Datastore datastorename | Get-VM | Get-VMQuestion | Answer-VMQuestion -DefaultOption  

To avoid being prompted to confirm the answer, you can add “-Confirm:$false” to each command.

More information on Answer-VMQuestion cmdlet (actually called Set-VMQuestion, but I prefer using its alias) located here: https://www.vmware.com/support/developer/windowstoolkit/wintk40u1/html/Set-VMQuestion.html

System Alert from SP of (REBOOT (watchdog reset)) CRITICAL | NetApp

Ran into this recently. Was upgrading SP in older FAS3270 HA pair running 7.3.6. I did software install, then sp upgrade. That’s when Cluster Takeover occured:

Mon Aug 22 08:59:47 MDT [cf.fsm.firmwareStatus:info]: Cluster monitor: partner dumping core  
Mon Aug 22 08:59:49 MDT [cf.ic.xferTimedOut:error]: wafl interconnect transfer timed out  
Mon Aug 22 08:59:50 MDT [cf.ic.xferTimedOut:error]: ofw interconnect transfer timed out  
Mon Aug 22 08:59:50 MDT [netif.linkDown:info]: Ethernet c0a: Link down, check cable.  

I have seen this before, and after checking the SP I did confirm it was indeed over 500 days uptime.

SP> sp uptime  
 15:02:17 up 759 days, 23:14, load average: 1.26, 1.27, 1.12

To fix this, I did a giveback, rebooted both SPs, and then could perform SP Upgrade successfully. You are prompted to reboot the SP after a successful upgrade, and I know I’ve been able to do this in the past without issue, but lesson learned – it’s better to perform SP reboot prior, than risk a takeover.

More from the KB article:

Service Processor Can Trigger Watchdog Reset After 500+ Days of Uptime:
Summary

The Service Processor (SP) contains a memory resource leak affecting the IPMI software, eventually causing the SP to become unresponsive and possibly triggering a watchdog reset of Data ONTAP®. In order to trigger this reset, the SP must be running for approximately five hundred (500) days or longer.

Symptom

The SP reports the following errors regularly when it is close to failing on the Data ONTAP console:

[hostname: statd: sp.network.link.down:warning]: Service Processor (SP) network port link down due to cable or network errors.
[hostname: statd: sp.network.link.down:warning]: Service Processor (SP) network port link down due to cable or network errors.
[hostname: statd: sp.network.link.down:warning]: Service Processor (SP) network port link down due to cable or network errors.
[hostname: orftp_rcv_file_from: sp.orftp.failed:warning]: SP communication error, receiver could not locate file on SP.
[hostname: statd: spmgmt.driver.hourly.stats:warning]: The software driver for the Service Processor (SP) detected a problem: Configuration Error (1). 
The following messages are reported in the SP’s Event Log proximate to the watchdog reset:

[IPMI.notice]: 1705 | c0 | OEM: ffff70005000 | ManufId: 150300 | SP Reset Externally
[IPMI.notice]: 1805 | c0 | OEM: fcff70000000 | ManufId: 150300 | POS Register: Unexpected Reset
[IPMI.notice]: 1905 | c0 | OEM: ffff70005000 | ManufId: 150300 | SP Reset Externally
[IPMI.notice]: 1a05 | c0 | OEM: fcff70000000 | ManufId: 150300 | POS Register: Unexpected Reset
[IPMI.notice]: 1b05 | c0 | OEM: ffff70005000 | ManufId: 150300 | SP Reset Externally
[IPMI.notice]: 1c05 | c0 | OEM: fcff70000000 | ManufId: 150300 | POS Register: Unexpected Reset
[IPMI.notice]: 1d05 | c0 | OEM: ffff70005000 | ManufId: 150300 | SP Reset Externally
[IPMI.notice]: 1e05 | c0 | OEM: fcff70000000 | ManufId: 150300 | POS Register: Unexpected Reset
[IPMI.notice]: 1f05 | c0 | OEM: ffff70005000 | ManufId: 150300 | SP Reset Externally
[IPMI.notice]: 2005 | c0 | OEM: fcff70000000 | ManufId: 150300 | POS Register: Unexpected Reset
[IPMI.notice]: 2105 | 02 | EVT: 6f01ffff | Partner_IO_Pre | Assertion Event, "Absent"
[IPMI.notice]: 2205 | 02 | EVT: 0301ffff | System_Fault | Assertion Event, "State Asserted"
[IPMI.notice]: 2305 | 02 | EVT: 0301ffff | Controller_Fault | Assertion Event, "State Asserted"
[IPMI.notice]: 2405 | 02 | EVT: 0300ffff | System_Fault | Assertion Event, "State Deasserted"
[IPMI.notice]: 2505 | 02 | EVT: 0301ffff | PSU1_Input_Type | Assertion Event, "State Asserted"
[IPMI.notice]: 2605 | 02 | EVT: 0301ffff | PSU2_Input_Type | Assertion Event, "State Asserted"
[IPMI.notice]: 2705 | 02 | EVT: 0301ffff | System_Fault | Assertion Event, "State Asserted"
[IPMI Event.critical]: NMI
[IPMI Event.critical]: L2 watchdog timeout hard reset
The messages in the Event Log will occur close enough to the watchdog reset that they cannot be used to predict failure. If a system restarts due to a watchdog reset, this signature can be used to verify if this issue caused the reset.  
Workaround

Run the SP CLI command, sp uptime to determine how long the SP has been running since the last reset.

Reboot the SP:

A reboot of the SP will clear any existing memory resource issues. This action is nondisruptive to data operations on the storage system. Once restarted, the SP will be able to run undisturbed for approximately the next five hundred days. The rate and severity of the leak is well characterized, this approach is a reasonable workaround to address the problem until the SP is updated with a fixed firmware release.

Caution: If the SP Firmware of your system is < 1.3 (FAS32xx/62xx platforms) or < 2.1 (FAS22xx platforms), you should be aware of BUG ID: 546048: Service Processor (SP) fails to come up after “sp reboot” command. Plan for a potential maintenance window to power-cycle the system, if needed.

Solution

Install a SP firmware release that mitigates this issue, once they are available.

In my case, for platform FAS3270, running Data ONTAP Release 7.3.x; the SP FW Release would be 1.3.3P2; which is what I installed.

More on the KB here: https://kb.netapp.com/support/index?page=content&id=7010141&locale=en_US