pepoluan
Cadet
- Joined
- Dec 1, 2013
- Messages
- 2
Hello, people! I've tried searching for something similar to my problem, but most of them are related to DHCP, which I am not using.
Here's my problem:
I've installed FreeNAS and configured a static IP address for it via the console. Then, I exposed its storage as an iSCSI target to another computer.
Every now and then, FreeNAS seems to have lost its IP address; pressing Enter on the console refreshes the display and shows that the URL has changed from http://10.11.12.13 to http://0.0.0.0
By selecting menu #1, then re0, then not choosing to delete/reset the interface, and choosing to not use DHCP, I found out that the previous configuration is still there. I just do a series of Enter's, and FreeNAS is back up with the static IP address.
As soon as the static IP address is restored, the servers connected to the iSCSI target all resume their connections without further ado. (Although I *do* have to restart some servers due to services failing).
What could possibly be the reason for this strange behavior?
This has happened 3 (three) times since Nov. 25, but there doesn't seem to be a pattern. First incident happened on Nov. 28. The next two incidents happened on Nov. 30. But since Saturday, the system has been running happily without further incidents.
Here's my problem:
I've installed FreeNAS and configured a static IP address for it via the console. Then, I exposed its storage as an iSCSI target to another computer.
Every now and then, FreeNAS seems to have lost its IP address; pressing Enter on the console refreshes the display and shows that the URL has changed from http://10.11.12.13 to http://0.0.0.0
By selecting menu #1, then re0, then not choosing to delete/reset the interface, and choosing to not use DHCP, I found out that the previous configuration is still there. I just do a series of Enter's, and FreeNAS is back up with the static IP address.
As soon as the static IP address is restored, the servers connected to the iSCSI target all resume their connections without further ado. (Although I *do* have to restart some servers due to services failing).
What could possibly be the reason for this strange behavior?
This has happened 3 (three) times since Nov. 25, but there doesn't seem to be a pattern. First incident happened on Nov. 28. The next two incidents happened on Nov. 30. But since Saturday, the system has been running happily without further incidents.