Status and Error Codes
CM 4000 Installation and Operating ManualR−6
The system did not receive a response from the bootp server (JNS). This message is typically logged
because the JNS control center is not running. A network problem is also possible. The system will
continue to operate using the previous application software and configuration. This will give unde-
sirable results if the configuration or software has changed since the last reboot. If no changes have
occurred, this should not be a problem.
26 Bootp failed: no vendor extensions.
This message is logged when a bad bootp response is received. The bootp response must have ven-
dor specific information to be useful. There may be another bootp server on the network erroneously
configured to reply to this system.
27 Bootp failed: no Jupiter extensions
This message is logged when a bad bootp response is received. The bootp response must have ven-
dor specific information to be useful. There may be another bootp server on the network erroneously
configured to reply to this system.
28 Bootp succeeded from server %s
This message indicates that a good bootp response was received from the indicated server.
29 Using configuration from %s for Bootp.
A valid bootp response was not received. The indicated source is supplying the required information.
2A Using bootline and defaults for Bootp.
A valid bootp response was not received. The built−in defaults are supplying the required informa-
tion.
2B Activate command received−−updating code.
The “activate” command was received. This is used to change the configuration set without reboot.
However, the system will reboot if the new configuration set contains changes that requires it.
2C Reboot command received−−rebooting
The “reboot” command was received. This is used to reboot the system.
2D Clear Persistent Memory command received−−memory will reinitialize on reboot.
The “clear persistent memory” command was received. This is used to clear the router status on the
next reboot. This has no immediate effect and any subsequent changes to router status will also be
cleared on the next reboot.
2E Post Mortem command received. Critical errors will not cause a reboot.
The “post−mortem” command was received. This is used to tell the system to not reboot on a fatal
error. The system tasks will be suspended so further investigation can be performed.
2F Unsupported %s command received−−ignored.
The system received an unsupported command. The system may be out of sync with the control cen-
ter. The command is ignored.
30 Scheduling system reboot
Because the system is a high−performance system a requested reboot will be deferred till the system
completes its high−priority tasks. This typically takes only a few seconds.
31 Scheduling configuration swap
Because the system is a high−performance system a requested configuration change will be deferred
till the system completes its high−priority tasks. This typically takes only a few seconds.
32 Checking CRC of %s
