Securepoint 2007 R2:
Fehler beim Versuch zu retten;
-- Illegale Namen
Ich habe nichts verändert. Ich habe nur eine Regel verändert und hinzugefügt, um eine Gruppe, die ich jetzt wieder gelöscht.
Wie kann ich diesen Fehler debug.
----------------------------------
Recieve error when trying to save;
-- illegal name
I have changed nothing. I only changed a rule order and added a group, which i have now deleted again.
How can i debug this error.
Fehler -- Illegale Namen
Moderator: Securepoint
Hi,
under which name did you try to save the config. You only get this message when you try to save the config under "default", this name is reserved by the system.
It's ok if you send your support question only in english!
under which name did you try to save the config. You only get this message when you try to save the config under "default", this name is reserved by the system.
It's ok if you send your support question only in english!
There are 10 types of people in the world... those who understand binary and those who don\'t.
Hi thank you for your reply, I had saved the configuration as 'MAIN' a few weeks ago using the Security Manager, and then set 'MAIN' to be the default startup config.
I have been able to save and reboot the device without any problems, overall it has been working semlessly in testing.
However all of a sudden, after making a couple of firewall changes (I think I may have deleted a service definition and changed a couple of rules), when I now go to save the configuration, I get an illegal name error, even though I never changed the name!
I also tried to save the config at the CLI, but i get the same error on the CLI.
rt2.monitor.york>
rt2.monitor.york> config running
MAIN
**
rt2.monitor.york> config save MAIN
-- illegal name
rt2.monitor.york>
Thank you for your time.
I have been able to save and reboot the device without any problems, overall it has been working semlessly in testing.
However all of a sudden, after making a couple of firewall changes (I think I may have deleted a service definition and changed a couple of rules), when I now go to save the configuration, I get an illegal name error, even though I never changed the name!
I also tried to save the config at the CLI, but i get the same error on the CLI.
rt2.monitor.york>
rt2.monitor.york> config running
MAIN
**
rt2.monitor.york> config save MAIN
-- illegal name
rt2.monitor.york>
Thank you for your time.
If i am right in thinking that it looks like the hard drive has become corrupt maybe, how can I export the otherwise perfect configuration instance in memory to another machine?
I have tried 'exporting' with the security manager but with no luck.
Thank you again for your time.
I have tried 'exporting' with the security manager but with no luck.
Thank you again for your time.
Ok,
the actual config lays under /tmp and is called "running.db". You can copy this file to another SP an try to save it there.
- You need a root user on both machines
- You have to install the programm "winscp"
- Open a connection via winscp to the SP with the "unknown error"
- Change to /tmp and copy the "running.db" to your local PC
- Connect to the second Sp and override the file withe databse on your PC
- Try to save the config on that SP
Good luck!
the actual config lays under /tmp and is called "running.db". You can copy this file to another SP an try to save it there.
- You need a root user on both machines
- You have to install the programm "winscp"
- Open a connection via winscp to the SP with the "unknown error"
- Change to /tmp and copy the "running.db" to your local PC
- Connect to the second Sp and override the file withe databse on your PC
- Try to save the config on that SP
Good luck!
There are 10 types of people in the world... those who understand binary and those who don\'t.
Sadly the HDD has gone beyond to point of no return!
login as: root
Using keyboard-interactive authentication.
Password:
Last login: Thu May 22 13:10:53 2008 from 192.168.200.101
# cd /
# ls
ls: I/O error
# cd /tmp
# ls
ls: I/O error
#
I have just ordered a new SSD instead to replace the HDD.
However, i must say i really am very impressed that securepoint is still running quite happily even though the HDD has completely died!
login as: root
Using keyboard-interactive authentication.
Password:
Last login: Thu May 22 13:10:53 2008 from 192.168.200.101
# cd /
# ls
ls: I/O error
# cd /tmp
# ls
ls: I/O error
#
I have just ordered a new SSD instead to replace the HDD.
However, i must say i really am very impressed that securepoint is still running quite happily even though the HDD has completely died!