Hi Atri,

Many thanks for your ideas. It is really helpful to produce a trend report.

With your directions I have planned to produce "Live user detail" report beyond the trend report. I found the below information usefull to produce "Live user detail" report from Object crasSessionEntry  - 1.3.6.1.4.1.9.9.392.1.3.21.1.

username of the session - crasUsername  1.3.6.1.4.1.9.9.392.1.3.21.1.1

duration of the session -  crasSessionDuration 1.3.6.1.4.1.9.9.392.1.3.21.1.6

session type - crasSessionProtocol    1.3.6.1.4.1.9.9.392.1.3.21.1.11.  The values of crasSessionProtocol are

1:other
2:ipsec
3:l2tp
4:l2tpoveripsec
5:pptp
6:l2f
7:ssl

I believe my above assumptions were right.

Thank you

-Senthil-

Hey Senthil,

I am glad I could be of assistance. If your question is answered please mark it as such and also rate the answer as it well help others locate this response faster.

If however you have any further questions regarding this issue then please let me know.

Regards,

Atri.

Hi Atri,

The Object name crasSessionTable in CISCO-REMOTE-ACCESS-MONITOR-MIB gives the remote access connection details.

crasSessionTable     ->     "This table lists all the currently active sessions.For each session, it lists the attributes (user,group, protocol, security), statistics packet and octets) and status."

But when I browse through the ALTIGA-SESSION-STATS-MIB, I see the below Object names as well

alActiveSessionTable (1.3.6.1.4.1.3076.2.1.2.17.2)          ->    "List of active sessions."

alPptpStatsSessionTable  (1.3.6.1.4.1.3076.2.1.2.3.3)     ->     "List of active sessions within tunnels."

Does ALTIGA-SESSION-STATS-MIB serves a different purpose? Or the same info is repetitive in CISCO-REMOTE-ACCESS-MONITOR-MIB?

Cheers

Senthil.S

Hey Senthil,

My apologies for the delayed response. Altiga Networks was a company that was acquired by Cisco which used to provide Virtual Private Networking in the US. The ALTIGA-SESSION-STATS-MIB was the MIB they had created for their sessions. It is highly likely that when the company was acquired to provide backward compatibility this MIB was retained while an indigenous MIB, the CISCO-REMOTE-ACCESS-MONITOR-MIB. This might have resulted in replication.

I would suggest that you use the CISCO-REMOTE-ACCESS-MONITOR-MIB.

Regards,

Atri.

Hi Puseth,

Many thanks you for the reference. Your post is very descriptive. I will check this in my device and then rate it.

Hi Atri,

I thank you for clarifying the difference between ALTIGA-SESSION-STATS-MIB and CISCO-REMOTE-ACCESS-MONITOR-MIB.

-Cheers-

Senthil

I achieved this by using the following OID's:

• How many concurrent sessions does the platform support (I.e: how many sessions is it licensed for)
  • OID = 1.3.6.1.4.1.9.9.392.1.1 (crasMaxSessionsSupportable)
  • Description = The maximum number of remote access sessions that may be supported on this device. If the device imposes no arbitrary limit on the maximum number of sessions, it should return a value of 0.
• How many concurrent users does the platform support (I.e: how many users is it licensed for)
  • OID = 1.3.6.1.4.1.9.9.392.1.2 (crasMaxUsersSupportable)
  • Description = The maximum number of remote access users for whom Remote Access sessions may be supported on this device. If the device imposes no arbitrary limit on the maximum number of users, it should return a value of 0.
  • Description =
• OID = 1.3.6.1.4.1.9.9.392.1.1 (crasNumSessions)
• Description = The number of currently active sessions. A session is a connection terminating on the managed entity which has been established to provide remote access connectivity to a user. A session is said to be 'active' if it is ready to carry application traffic between the user and the managed entity. A session which is not active is defined to be 'dormant'.How many concurrent sessions are there ?

This way you can easily track if your VPN-utilization (sessions & users)  is trending towards your license-limit or HW-limit.

GReetz,

S.