Guest

Preview Tool

Cisco Bug: CSCsz82813 - MCP does not retain changes for multi-context FWSM contexts

Last Modified

Nov 10, 2016

Products (1)

  • Cisco Security Manager

Known Affected Releases

3.2(1)

Description (partial)


Symptom:


MCP does not retain changes for multi-context FWSM contexts' host names which are configured in 'hosts' file of windows server.
Conditions:

MCP can only manage 5 contexts in a multicontext FWSM due to ASDM session limit of 5 to the admin context. Workaround is to edit individual contexts to IP address rather than "admin ip". This gives a display issue whereby the context is displayed as the ip address rather than the context name. Workaround for this is to add the context and IP address to the CSM server hosts table. However, in this case, CSM does not retain the edited IP address but rather reverts to the "admin ip" setting. Therefore, delete the entries from the hosts table and live with the ip address rather than the context name.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.