Under certain conditions you may find that the NM-CIDS bootloader has been changed by mistake to load from the "secondary" instead of the "primary" partition. This configuration change could have been made by mistake when booted into the bootloader and running the following command:
ServicesEngine boot-loader> config
The bootloader should never be changed from the default of "primary". The difficulty that this creates is that there are no visually configurable options that would allow you to change back into the primary parition once the configuration has been changed. Because of this the NM-CIDS will be stuck booting in the Cisco Cache Engine and you will not be able to load the module.
Below is a screenshot of what the Cisco Cache Engine boot looks like and the list of avaliable options. None of these options will change the boot back to primary:
In order to get the NM-CIDS to boot into the primary partition, reset the module. During the boot when it says "System now booting...." press the "i" key. It will not prompt you to press the "i". It is a hidden command and you just need to press it at the right time.This will load the primary boot loader and from here you should be albe to fix the configuration. Keep in mind that you will still need to hit the *** when the NM-CIDS boots and run "config" to permanently change back to the primary bootloader partition.
Dearsi have a question for sandboxing, how is the process from for the file to reach to sandbox, below is what I understand please correct if it is wrongunknown files arrives on FW FW send to sandbox appliance or cloud ( here the connection tra...
hi everyone, the problem - unfortunately we have just 1 cli admin user and we have know idea what is the password. after how many unsuccessful attempts user is going to blocked state and how long it will be in blocked state. if forever so we have to ...
ISE 3.0 patch 2AnyConnect 4.10 Hello, When we attempt to add anyconnect configuration package from below: client provisioning --> Resources --> anyconnect configuration We get the following error. "Exception encountered. Una...