CISCO ASA SNMP

VPN Users logged in using CISCO VPN clients

regards
Chandru

Hi,

You can easily accomplish this using a VPN Analyzer. Below are good examples;

Adventnet Firewall Analyzer      www.adventnet.com
FirePlotter      www.fireplotter.com
AlgoSec Firewall Analyzer      www.algosec.com
WallWatcher      www.wallwatcher.com
Firewall Analyzer      www.kdware.com
SawMill                www.sawmill.net

Enabling SNMP

The SNMP agent that runs on the security appliance performs two functions:

"Replies to SNMP requests from NMSs.

"Sends traps (event notifications) to NMSs.

To enable the SNMP agent and identify an NMS that can connect to the security appliance.

Step 1 Ensure that the SNMP server on the security appliance is enabled
hostname(config)# snmp-server enable

Step 2 To identify the IP address of the NMS that can connect to the security appliance.

hostname(config)# snmp-server host interface_name ip_address [trap | poll] [community
text] [version 1 | 2c] [udp-port port]


Specify trap or poll if you want to limit the NMS to receiving traps only or browsing (polling) only.

Step 3 To specify the community string,

hostname(config)# snmp-server community key

Step 4 (Optional) To set the SNMP server location or contact informatio

hostname(config)# snmp-server {contact | location} text

Step 5 To enable the security appliance to send traps to the NMS.

hostname(config)# snmp-server enable traps [all | syslog | snmp [trap] [...] |
entity [trap] [...] | ipsec [trap] [...] | remote-access [trap]]

The default configuration has all snmp traps enabled (snmp-server enable traps snmp authentication linkup linkdown coldstart). You can disable these traps using the no form of this command with the snmp keyword. However, the clear configure snmp-server command restores the default enabling of SNMP traps.

If you enter this command and do not specify a trap type, then the default is syslog. (The default snmp traps continue to be enabled along with the syslog trap.)

Traps for snmp include:

"authentication

"linkup

"linkdown

"coldstart

Traps for entity include:

"config-change

"fru-insert

"fru-remove

Traps for ipsec include:

"start

"stop

Traps for remote-access include:

"session-threshold-exceeded

Step 6 To enable system messages to be sent as traps to the NMS.

hostname(config)# logging history level

You must also enable syslog traps using the preceding snmp-server enable traps command.

Step 7 To enable logging, so system messages are generated and can then be sent to an NMS.

hostname(config)# logging enable

example:
hostname(config)# snmp-server host 192.168.3.2

hostname(config)# snmp-server location building 42

hostname(config)# snmp-server contact rootcoolk

hostname(config)# snmp-server community cisco

Hey thanks "uetian1707", I appreciate you jumping into my question!


From the CLI (without downloading and installing any software or relying on a GUI), you could just login to the ASA, go to enable mode, then type something like:
 sh ipsec sa det | grep current_peer

and get an output like:
      current_peer: 1.2.3.4, username: username1
      current_peer: 5.6.7.8, username: username2
      current_peer: 9.10.11.12, username: username3

(IPs/usernames are fakes of course, but the output is right from one of my ASAs)
(and the full command is  "show ipsec sa detail | grep current_peer". Check it out without the grep to see all the info in there, it's a lot!)

MAN there are a LOT of question stealers out today! Thanks Guys, way to go! With lots of extraneous information and overcomplicated pseudo solutions too, SWEET!

Thanks!

Can i get the information using OID as i am trying to get this information from our NMS?

Thanks!!

Is there any reason why the username is not displayed as part of the other SNMP strings?

regards
Chandru

No telling what reasoning goes into designing a MIB by any given vendor, and it MAY be in there somewhere, but I walked the mib to double check that perhaps it was in a MIB i didn't have loaded, but I saw no usernames in there anywhere.

But between polling the MIBs and parsing your syslog outputs in your NMS, you should be able to get what you want.

Any success in resolving this issue? Did I answer your question?

Sorry for the delay in getting back to you on this?
I am still not able to get the usernames in SNMP or using OID?
Is there no way of getting this information? Can you let me know how to setup the syslog to get only the userlogin information?

regards
Chandru