Submit a ticketCall us
Home > Success Center > Archive > 2018January24 - FSM Delete > Firewall Security Manager (FSM) > View ASA multiple contexts

View ASA multiple contexts

Table of contents
Created by Justin Rouviere, last modified by Karen Valdellon on Jun 30, 2017

Views: 1,330 Votes: 0 Revisions: 5


In ASA multi-context firewalls, there is one admin context and multiple user contexts. The admin context only specifies the interface assignments to each user context, and there is no firewall rule or object definition. The user context contains the firewall rules or object definition and works as a separate firewall. FSM only analyzes the user context.


The admin context also has one special interface for firewall management purposes. The FSM connector can access each user context directly or access the user context through the admin context, for example, connecting to the admin context via the management interface, and then switching from the admin context to the user context.

Basically, the FSM connector uses the admin context as a jumper.


FSM treats each user context as a separate firewall. Each user context consumes one license seat.


FSM does NOT analyze the admin context. The admin context config does NOT consume any license seat.


See the FSM FAQ on THWACK for more information.


All FSM versions


  1. Go to the following FSM location:
    C:\Program Files\SolarWinds\SolarWinds FSMServer\conf\ScriptTemplates\csa_admin_context
  2. Copy the two .script files to the FSM install location \SolarWinds FSMServer\conf\ScriptTemplates.
  3. Restart FSM.
  4. Import through the Connect to Device connector and click Finish.
  5. In the device command template drop-down menu, select Cisco Security Appliance using Admin Context and select Show internal Command template parameters.
  6. In the Contextname value, specify the name of the context that needs to be extracted.

Use the Cisco Security Appliance using Admin Context only for devices that have multiple devices that are accessible only through the system context. In this instance, the device name or IP address must refer to the admin context where a connection is being sought.


Suggested tags : FSM, ASA, multi-context, multiple, context, admin, import, add, firewall, Cisco



 Reason for Rework or Feedback from Technical Content Review:   


Last modified