08-27-2004 04:13 AM - edited 03-09-2019 08:37 AM
We just migrated one of my customer IDS 4235 from version 3.x to 4.1(1)S47 using the Ugrade/Recovery CD 4.1
We are trying to apply basic configuration like changing the hostname & IP address by using the CLI command "SETUP". Everytime we apply the changes by selecting the appropriate item (2 - Save this configuration and exit setup), im getting this error "Error: Could not restart the network services. Fatal Error has occurred. Node MUST be rebooted to enable alarming."
Listed below is the output that we have captured during the initial configuration process:
sensor# setup
--- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
User ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Current Configuration:
networkParams
ipAddress 10.1.9.201
netmask 255.255.255.0
defaultGateway 10.1.9.1
hostname sensor
telnetOption disabled
accessList ipAddress 10.0.0.0 netmask 255.0.0.0
exit
timeParams
summerTimeParams
active-selection none
exit
exit
service webServer
general
ports 443
exit
exit
Current time: Thu Aug 26 10:13:29 2004
Setup Configuration last modified: Thu Aug 26 10:12:46 2004
Continue with configuration dialog?[yes]:
Enter host name[sensor]: IDS02
Enter IP address[10.1.9.201]: 10.1.2.4
Enter netmask[255.255.255.0]:
Enter default gateway[10.1.9.1]:
Enter telnet-server status[disabled]:
Enter web-server port[443]:
Modify current access list?[no]:
Modify system clock settings?[no]:
The following configuration was entered.
networkParams
ipAddress 10.1.2.4
defaultGateway 10.1.9.1
hostname IDS02
accessList ipAddress 10.0.0.0 netmask 255.0.0.0
exit
timeParams
summerTimeParams
active-selection none
exit
exit
service webServer
general
ports 443
exit
exit
[0] Go to the command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration and exit setup.
Enter your selection[2]: 2
Error: Could not restart the network services. Fatal Error has occurred. Node MUST be rebooted to enable alarming.
I'm getting also the same error on the first IDS 4235 that we have just purchased, pre installed with 4.1. Everytime we changed the IP Address, we are receiving the same error w/c is "Error: Could not restart the network services. Fatal Error has occurred. Node MUST be rebooted to enable alarming."
I'm just wondering bec prior to this, we have changed the IP address & the gateway for a couple of times & we dont have that kind of problem. The changing of IP address was done during the testing phase of the activities & the problem came up only when we have already put that IDS on production. My customer just needed to change the IP address bec of some changes in the network.
We tried to restart both IDS but the problem remains.
I'm trying to get some technical info on TAC website but i cant find anything.
Hope you can help me on this one.
Thank you very much.
Solved! Go to Solution.
08-27-2004 07:21 AM
your default gateway is incorrect. fix that, and you should be good to go.
thanks,
chris
08-27-2004 07:41 AM
You are getting a generic error message that means that either the ip, netmask, or def gw are incorrect. You need to enter valid data (you did not enter the default gateway).
The Fatal part of the messages simply means that after the first failure the previous config was applied and that also failed.
The sensor is issuing "ifconfig" and "route" commands and one or both of them is failing.
08-27-2004 07:21 AM
your default gateway is incorrect. fix that, and you should be good to go.
thanks,
chris
08-27-2004 07:41 AM
You are getting a generic error message that means that either the ip, netmask, or def gw are incorrect. You need to enter valid data (you did not enter the default gateway).
The Fatal part of the messages simply means that after the first failure the previous config was applied and that also failed.
The sensor is issuing "ifconfig" and "route" commands and one or both of them is failing.
08-28-2004 01:02 AM
Thank you very much.
Both problem i have with the 2 IDS was resolved.
It was indeed a wrong default gateway.
Thanks again chris & james =>
Perry
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide