NVRAM failure can be a big problem. Doing a DBDOC Live Loop Annotation fetching the block specifications will fail if the NVRAM has failed. This could be useful information to you.
A client reported that DBDOC Hyperview could not fetch the specs of a block. In fact, the specs could not be fetched in any block in that module. This is shown in this image. Live data could be fetched - only the reporting of the specifications was affected.
However, fetching specs worked fine in other modules. The example in a clone of the problem one, as you can see.
What could cause this problem?
The next two images show the difference between working and failing module status fetches.
Guess what? The problem module shows NVRAM failure status: Fail. The one that is working says: Good.
From the Client
"I believe a NVRAM failure will prevent looking at any of the configuration."
"The module will continue to operate with an NVRAM error because a copy of the configuration is held in SRAM and executes from there. The next time the module is reset it will not startup but will fail.
"This module had failed earlier and was hard initialized during an outage and did not show the errors, but has NVRAM failure now."
New INFI 90 "art" has been crafted. This is the first time we know of that the module status fetch we created has been used to solve a problem.