Pages

Wednesday, May 21, 2014

Cisco VPN LAB 1: Simple Easy VPN Example between Routers

VPN Lab Series:
Cisco VPN LAB 1 : Simple Easy VPN Example between Routers and Comparison with DMVPN
Cisco VPN LAB 2 : IPSec VPN Example Between Two ASA 8.4.2
Cisco VPN LAB 3 : EZ VPN Between ASA 8.4.2, IOS Router and EZVPN Client Software

Working on Easy VPN and DMVPN, I completed this first lab for EZVPN lab and also list some using resource at the bottom of this post.

1. Topology


It is still with my favorite IOU rack v3. The physical connection with IP addresses have been shown on the diagram.

R1 will be easy VPN server and R2 will be the client. This lab will show how to configure a basic easy vpn client / server set up. R3 and R6 will be only used to do test ping with only default route and interface ip configured on them.

2. Configuration: (Redundancy configuration have been omitted)




@EZVPN Server Configuration
R1#show run
Building configuration...

Current configuration : 2631 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
security passwords min-length 1

!--- Enable Authentication, Authorizing and Accounting (AAA)
!--- for user authentication and group authorization.
aaa new-model
!--- Enable the AAA commands in order 
!--- to enable Xauth for user authentication.
aaa authorization network hw-client-groupname local 
!--- Enable the AAA commands
!--- in order to enable group authorization.
aaa authorization network groupauthor local 
!
!
!         
!
aaa session-id common
clock timezone CST 8
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip source-route
!
ip cef
no ip domain lookup
no ipv6 traffic interface-statistics
no ipv6 cef
!
multilink bundle-name authenticated

!--- Define the username and password to use for Xauth.
username cisco password 0 cisco123
!
redundancy

!--- Create an Internet Security Association and
!--- Key Management Protocol (ISAKMP) policy for Phase 1 negotiations.
crypto isakmp policy 1
 authentication pre-share
 group 2
crypto isakmp client configuration address-pool local dynpool
!
!--- Create a group with the pre-shared key for IKE authentication.
crypto isakmp client configuration group hw-client-groupname
 key hw-client-password

!--- Create the Phase 2 policy for actual data encryption.
crypto ipsec transform-set transform-1 esp-des esp-sha-hmac 
!
!--- Create a dynamic map and
!--- apply the transform set that was created earlier.
crypto dynamic-map dynmap 1
 set transform-set transform-1 
 reverse-route
!
!--- Create the actual crypto map,
!--- and apply the AAA lists that were created earlier.
!--- These commands associate the AAA commands to the crypto map.
crypto map dynmap isakmp authorization list hw-client-groupname
crypto map dynmap client configuration address respond
crypto map dynmap 1 ipsec-isakmp dynamic dynmap 
!
!--- Apply the crypto map on the interface where
!--- traffic leaves the router.
interface Ethernet0/0
 description connected to Internet
 ip address 20.20.20.2 255.255.255.0
 crypto map dynmap
!
interface Ethernet0/1
 no ip address
 shutdown 
!
interface Ethernet0/2
 ip address 30.30.30.1 255.255.255.0
!
!
ip forward-protocol nd
!
!         
no ip http server
no ip http secure-server
ip route 0.0.0.0 0.0.0.0 Ethernet0/0
!
!
control-plane
!
!
line con 0
 logging synchronous
line aux 0
line vty 0 4
!
exception data-corruption buffer truncate

end

@EZVPN Client Configuration
R2#sh run
Building configuration...

Current configuration : 2420 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
security passwords min-length 1
!
aaa new-model
!
!
aaa authentication login userauthen local
aaa authorization network groupauthor local 
!
aaa session-id common
clock timezone CST 8
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip source-route
!
!
ip cef
no ip domain lookup
ip domain name cisco.com
no ipv6 traffic interface-statistics
no ipv6 cef
!
multilink bundle-name authenticated
!
username cisco password 0 cisco123
!
redundancy
!--- Set the parameters to connect to the 
!--- appropriate Easy VPN group on the Easy VPN server.
crypto ipsec client ezvpn hw-client
 connect auto
 group hw-client-groupname key hw-client-password
 mode client
 peer 20.20.20.2
 xauth userid mode interactive
!
!--- Use the crypto ipsec client ezvpn <name> command on the
!--- interface that connects to the Easy VPN server
!--- in order to complete the Easy VPN.
interface Ethernet0/0
 description INTERNET
 ip address 20.20.20.1 255.255.255.0
 crypto ipsec client ezvpn hw-client


!--- Define the inside interfaces that will access 
!--- and can be accessed via Easy VPN.
interface Ethernet0/1
 description LAN
 ip address 10.10.10.1 255.255.255.0
 crypto ipsec client ezvpn hw-client inside
!
interface Ethernet0/2
 no ip address
 shutdown
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
ip route 0.0.0.0 0.0.0.0 Ethernet0/0
!
control-plane
!
!
line con 0
 logging synchronous
line aux 0
line vty 0 4
!
exception data-corruption buffer truncate
end

3. Verify

R2#show crypto ipsec sa

interface: Ethernet0/0
    Crypto map tag: Ethernet0/0-head-0, local addr 20.20.20.1

   protected vrf: (none)
   local  ident (addr/mask/prot/port): (30.30.30.20/255.255.255.255/0/0)
   remote ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
   current_peer 20.20.20.2 port 500
     PERMIT, flags={origin_is_acl,}
    #pkts encaps: 0, #pkts encrypt: 0, #pkts digest: 0
    #pkts decaps: 0, #pkts decrypt: 0, #pkts verify: 0
    #pkts compressed: 0, #pkts decompressed: 0
    #pkts not compressed: 0, #pkts compr. failed: 0
    #pkts not decompressed: 0, #pkts decompress failed: 0
    #send errors 0, #recv errors 0

     local crypto endpt.: 20.20.20.1, remote crypto endpt.: 20.20.20.2
     path mtu 1500, ip mtu 1500, ip mtu idb Ethernet0/0
     current outbound spi: 0x2B595786(727275398)
     PFS (Y/N): N, DH group: none

     inbound esp sas:
      spi: 0xD56D693B(3580717371)

R2#show crypto ipsec client ezvpn 
Easy VPN Remote Phase: 8

Tunnel name : hw-client
Inside interface list: Ethernet0/1
Outside interface: Ethernet0/0
Current State: IPSEC_ACTIVE
Last Event: MTU_CHANGED
Address: 30.30.30.20 (applied on Loopback10000)
Mask: 255.255.255.255
DNS Primary: 30.30.30.10
DNS Secondary: 30.30.30.11
NBMS/WINS Primary: 30.30.30.12
NBMS/WINS Secondary: 30.30.30.13
Default Domain: cisco.com
Save Password: Disallowed
Current EzVPN Peer: 20.20.20.2

When ping from R2 (10.10.10.1) to R6 (30.30.30.30) and show crypto ipsec sa, we see encrypted packet is 5 but decrypted packet is 4. That is because first ping packet failed to reach the destination as we can see it from ping following result. After that, all ping packets will be encrypted and decrypted properly.

R2#ping 30.30.30.30 source 10.10.10.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 30.30.30.30, timeout is 2 seconds:
Packet sent with a source address of 10.10.10.1
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 4/5/8 ms

R2#show crypto ipsec sa            

interface: Ethernet0/0
    Crypto map tag: Ethernet0/0-head-0, local addr 20.20.20.1

   protected vrf: (none)
   local  ident (addr/mask/prot/port): (30.30.30.20/255.255.255.255/0/0)
   remote ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
   current_peer 20.20.20.2 port 500
     PERMIT, flags={origin_is_acl,}
    #pkts encaps: 5, #pkts encrypt: 5, #pkts digest: 5
    #pkts decaps: 4, #pkts decrypt: 4, #pkts verify: 4
    #pkts compressed: 0, #pkts decompressed: 0
    #pkts not compressed: 0, #pkts compr. failed: 0
    #pkts not decompressed: 0, #pkts decompress failed: 0
    #send errors 0, #recv errors 0

******Some Other Resources. 

From Cisco page:

  • Cisco Enhanced Easy VPN and DMVPN Comparison


Service/Feature Name

Enhanced Easy VPN

DMVPN

Scalability per Hub

Large number of spokes can be supported per hub

Depends on routing protocol chosen

Identical Configuration for All Spokes

Yes

No

Cross-Platform Support

Yes

No

Support for Software/Hardware Client

Yes

No software client support

Stateful Failover

No; but available with legacy Easy VPN

Depends on routing protocol for recovery

Always up Tunnel to Hub

Not required

Yes

Support for Multicast Traffic

Yes

Yes

Spoke-to-Spoke Direct Communication

No

Yes

Support for QoS

Yes

Yes

Support for Routing Protocols

No

Yes

Support for Certificates

Yes

Yes


  • Cisco Site-to-Site VPN Solution Comparison

Cisco GET-VPN

Cisco DMVPN

Cisco GRE-Based VPN

Cisco Easy VPN

Standard IPsec VPN

Tunnel-less VPN

Tunnel-based VPN

Customer Benefits

• Simplifies encryption integration on IP and Multiprotocol Label Switching (MPLS) WANs

• Simplifies encryption management through use of "group laying" instead of point-to-point key pairs

• Enables scalable and manageable any-to-any connectivitiy between sites

• Supports quality of services (QoS) multicase and routing

• Simplifies encryption of configuration and management for point-to-point GRE tunnels

• Supports QoS, multicast, and routing

• Enable transport of multicast and routing traffic across an IPsec VPN

• Support non-IP protocols

• Supports QoS

• Simplifies IPsec and remote-site device management through dynamic configuration policy-push

• Supports QoS

• Provides encryption between sites

• Supports QoS

When to Use

• Add encryption to MPLS or IP WANs while preserving any-to-any connectivity and networking features

• Other scalable, full-time meshing for IPsec VPNS

• Enables participation of smaller routers in meshed networks

• Simplifies encryption key management while supporting routing, QoS, and multicast

• Simplifies configuration for hub-and-spoke VPNs while supporting routing, QoS, and multicast

• Provides low-scale, on-demand meshing

• Use when routing must be supported across the VPN

• Use for same functions as hub-and-spoke DMVPN, but it requires more detailed configuration

• Use when simplifying overall VPN

• Configuration and management is the primary goal but only limited networking features are required

• Use to provide simple, unified configuration framework for mix of Cisco VPN products

• Use when multivendor interoperability is required

Product Interoperability

Cisco routers only

Cisco routers only

Cisco routers only

Cisco ASA 5500 Series, Cisco VPN 3000 Series, and Cisco PIX® Firewall

Mutlivendor

Scale

Thousands

Thousands hub and spoke; hundreds partially meshed spoke-to-spoke connections

Thousands

Thousands

Thousands

Provisioning and Management

CLI Cisco Security Manager

Cisco Security Manager and Cisco Router and Security Device Manager

Cisco Security Manager and Cisco Router and Security Device Manager

Configuration automatically pushed to remote sites from headend; headend policies defined in Cisco Security Manager or Cisco Router and Security Device Manager

Cisco Security Manager and Cisco Router and Security Device Manager

Topology

Hub and spoke; any-to-any

Hub and spoke on-demand spoke-to-spoke partial mesh; spoke-to-spoke connections automatically terminated when no traffic present

Hub and spoke; small-scale meshing as manageability allows

Hub and spoke

Hub and spoke; small-scale meshing as manageability allows

Routing

Supported; Cisco GET-VPN any-to-any connectivity capability can also be used to provide secure routing across any entire router backbone

Supported

Supported

Not Supported

Not Supported

QoS

Supported

Supported

Supported

Supported but QoS policy is not dynamically pushed to the remote sites

Supported

Multicast

Natively supported across MPLS and private IP networks, tunneled across Internet-based WANs

Tunneled

Tunneled

Not Supported

Not Supported

Non-IP Protocols

Not Supported

Not Supported

Supported

Not Supported

Not Supported

Private IP Addressing

Requires use of GRE or DMVPN with Cisco GET-VPN to support private addresses across public Internet backbones

Supported

Supported

Supported

Supported

High Availability

Routing

Routing

Routing

Stateless failover

Stateless failover


Sunday, May 18, 2014

Enabling SNMP v3 - Part 1: Cisco IOS Devices - Disable SNMP v1 and SNMP v2c

1. Enable SNMPv3

It is time to retire SNMPv2 on our network environment. Here is sample configuration for all of our Cisco devices. Some of old devices do not support AES , then DES will be the choice.

ip access-list standard snmp-Allow
permit 192.168.1.0 0.0.0.255

snmp-server view ReadAccess iso included

snmp-server view ReadAccess 1.3.6.1.6.3.18 excluded
snmp-server view ReadAccess 1.3.6.1.6.3.16 excluded
snmp-server view ReadAccess 1.3.6.1.6.3.15 excluded
snmp-server view ReadAccess 1.3.6.1.2.1.4.21 excluded
snmp-server view ReadAccess 1.3.6.1.2.1.4.22 excluded

snmp-server view ReadAccess iso included
snmp-server view ReadAccess internet included
snmp-server view ReadAccess system included
snmp-server view ReadAccess interfaces included
snmp-server view ReadAccess chassis included
snmp-server view WriteAccess iso included
snmp-server view WriteAccess internet included
snmp-server view WriteAccess system included
snmp-server view WriteAccess interfaces included
snmp-server view WriteAccess chassis included

snmp-server view WriteAccess iso included

snmp-server view WriteAccess 1.3.6.1.6.3.18 excluded
snmp-server view WriteAccess 1.3.6.1.6.3.16 excluded
snmp-server view WriteAccess 1.3.6.1.6.3.15 excluded
snmp-server view WriteAccess 1.3.6.1.2.1.4.21 excluded
snmp-server view WriteAccess 1.3.6.1.2.1.4.22 excluded

snmp-server group AccessRW v3 priv read ReadAccess write WriteAccess  access snmp-Allow

snmp-server group AccessRO v3 priv read ReadAccess access snmp-Allow

snmp-server user NetServices-RW  AccessRW v3 auth sha cisco priv aes 128 cisco

snmp-server user NetServices-RO AccessRO v3 auth sha cisco priv aes 128 cisco


snmp-server host 192.168.1.40 trap version 3 priv NetService-RO


snmp-server enable traps

2. Disable SNMP v1 and SNMP v2C

CiscoTest#show snmp group 
groupname: ILMI                             security model:v1 
contextname: <no context specified>         storage-type: permanent
readview : *ilmi                            writeview: *ilmi                           
notifyview: <no notifyview specified>       
row status: active

groupname: ILMI                             security model:v2c 
contextname: <no context specified>         storage-type: permanent
readview : *ilmi                            writeview: *ilmi                           
notifyview: <no notifyview specified>       
row status: active

groupname: SNMPv3-RO                        security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : ReadView-All                     writeview: <no writeview specified>        
notifyview: <no notifyview specified>       
row status: active      access-list: snmp-Allow

groupname: SNMPv3-RW                        security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : ReadView-All                     writeview: WriteView-All                   
notifyview: <no notifyview specified>       
row status: active      access-list: snmp-Allow

groupname: NetService-RO                    security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : <no readview specified>          writeview: <no writeview specified>        
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F
row status: active

CiscoTest(config)#no snmp-server group ILMI v1
CiscoTest(config)#no snmp-server group ILMI v2c
CiscoTest(config)#do sh snmp group
groupname: SNMPv3-RO                        security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : ReadView-All                     writeview: <no writeview specified>        
notifyview: <no notifyview specified>       
row status: active      access-list: snmp-Allow

groupname: SNMPv3-RW                        security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : ReadView-All                     writeview: WriteView-All                   
notifyview: <no notifyview specified>       
row status: active      access-list: snmp-Allow

groupname: NetService-RO                    security model:v3 priv 
contextname: <no context specified>         storage-type: nonvolatile
readview : <no readview specified>          writeview: <no writeview specified>        
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F
row status: active

Unfortunately those groups will come back after system rebooted. Best way is to remove them from system view by following commands:

snmp-server view *ilmi system excluded
snmp-server view *ilmi atmForumUni excluded
snmp-server view v1default iso excluded

R-Test-Lab#show snmp view
*ilmi system - excluded nonvolatile active
*ilmi atmForumUni - excluded nonvolatile active
cac_view pimMIB - included read-only active
cac_view msdpMIB - included read-only active
cac_view interfaces - included read-only active
cac_view ip - included read-only active
cac_view ospf - included read-only active
cac_view bgp - included read-only active
cac_view dot1dBridge - included read-only active
cac_view ifMIB - included read-only active
cac_view nhrpMIB - included read-only active
cac_view ipMRouteStdMIB - included read-only active
cac_view igmpStdMIB - included read-only active
cac_view ipForward - included read-only active
cac_view ipTrafficStats - included read-only active
cac_view ospfTrap - included read-only active
cac_view sysUpTime.0 - included read-only active
cac_view ciscoPingMIB - included read-only active
cac_view ciscoIpSecFlowMonitorMIB - included read-only active
cac_view ciscoIpSecPolMapMIB - included read-only active
cac_view ciscoPimMIB - included read-only active
cac_view ciscoMgmt.187 - included read-only active
cac_view ciscoIfExtensionMIB - included read-only active
cac_view ciscoEigrpMIB - included read-only active
cac_view ciscoCefMIB - included read-only active
cac_view ciscoNhrpExtMIB - included read-only active
cac_view ciscoIpMRouteMIB - included read-only active
cac_view ciscoIPsecMIB - included read-only active
cac_view cospf - included read-only active
cac_view ciscoExperiment.101 - included read-only active
cac_view ciscoIetfIsisMIB - included read-only active
cac_view ciscoIetfBfdMIB - included read-only active
cac_view ifIndex - included read-only active
cac_view ifDescr - included read-only active
cac_view ifType - included read-only active
cac_view ifAdminStatus - included read-only active
cac_view ifOperStatus - included read-only active
cac_view snmpTraps.3 - included read-only active
cac_view snmpTraps.4 - included read-only active
cac_view snmpTrapOID.0 - included read-only active
cac_view internet.6.3.1.1.4.3.0 - included read-only active
cac_view lifEntry.20 - included read-only active
cac_view cciDescriptionEntry.1 - included read-only active
v1default iso - excluded nonvolatile active
v1default internet.6.3.15 - excluded permanent active
v1default internet.6.3.16 - excluded permanent active
v1default internet.6.3.18 - excluded permanent active
v1default ciscoMgmt.394 - excluded permanent active
v1default ciscoMgmt.395 - excluded permanent active
v1default ciscoMgmt.399 - excluded permanent active
v1default ciscoMgmt.400 - excluded permanent active

Monday, May 12, 2014

Checkpoint UTM-1 Edge X Configuration Tips and Resources

Still having some Sofaware UTM-1 Edge devices in our production environment. They are perfectly support by Checkpoint Management Server when using firmware 8.2.50



There is a couple of things admin needs to pay attention to:

1. Local Firewall rules take precedence on Security Management Server Policies

If you are using Security Management Server to do central management, the local rules in Edge device has to be disabled or deleted, else it will take effect before the security policies from management server.

2. SNMPv3 does not support


3. Port 981 is for remote management


4. Set Time to sync with a NTP time server in the Tools of Setup menu.

Note: The switch to daylight saving time does not affect UTC. It refers to time on the zero or Greenwich meridian, which is not adjusted to reflect changes either to or from Daylight Saving Time.

5. SSH to the edge device

You are able to log into Edge device through SSH. There are some other interesting things to do with SSH. You can find one post regarding CheckPoint VPN-1/UTM Edge automatic SSH login

6. Reset Checkpoint Edge and SofaWare box to defaults

Please do the following:
  • Unplug the power cord.
  • Hold the reset button on the back of the box.
  • Plug in the power cord while holding the button until the pwr/sec led is steady red.
  • Leave the reset button for 3 seconds.
  • Press the reset button again for 10 seconds until the pwr/sec led starts blinking red.
  • Reconfigure your box and install certs.

7. Inside Check Point Edge Device from Notes from a CCSE+ Lanchmann Blog


  • The Edge X runs with a MIPS CPU from Brecis with 166 MHz.
  • The operating system is a uCLinux running kernel 2.4.20.
  • As filesystem SquashFS is used along with LZMA compression.
  • WiFi is provided by Atheros.

8. Some other good resources I found from the Internet:

Tuesday, May 6, 2014

Enabling SNMP v3 Part 2: Checkpoint R75 (Gaia & Splat) (AES and SHA Configuration)

This post is second part of SNMPv3 configuration. First part is in this post for Cisco devices.

During setting up SNMPv3 on checkpoint appliance, there are some steps and notes found useful. I put them together for future reference.


1.  SNMP General Settings:


2. V3 - user-based Security Model (USM)

Authentication is using MD5
Privacy is using DES.
If you want to change SHA or AES, you have to use command line to add SNMP V3 user. All steps have been listed at Step 4.

 3. Enabled Traps

 4. Trap Receivers Settings


For command lines, here is a good post for it on pingtool.org. Some configuration are copied here :

set snmp agent on
set snmp contact "zzzz@domain.com"
set snmp location "Middle of nowhere"
add snmp address 123.34.56.78
set snmp agent-version v3-Only
add snmp usm user snmpv3user security-level authPriv auth-pass-phrase 111222333 privacy-pass-phrase 555666777


Notes: By Default, at WebGUI, Checkpoint SNMPv3 only support MD5 and DES for Authentication typle and Privacy Type. Make sure when setting up SNMP manager server, you choose MD5 and DES.


CP> show snmp 
addresses     - snmp agent address
agent         - snmp daemon
agent-version - snmp version
community     - snmp agent community
contact       - snmp Contact
location      - snmp Location
traps         - snmp Traps
usm           - SNMPv3 USM (User-based Security Model)


CP> show snmp usm user ReadView-All
Username ReadView-All
Security Level authPriv
Authentication Type MD5
Privacy Type DES

Note: From Command Line, Checkpoint can manually add a SNMPv3 user to use SHA or AES by following these steps to configure SNMPv3 users on Gaia OS to use SHA (SHA1) / AES authentication from SK97692:

4.1.Connect to command line on Gaia OS machine (over SSH, or console). 

4.2.Log in to Clish. 

4.3.Stop the SNMP Agent from Clish: 
HostName> set snmp agent off 

4.4.Log in to Expert mode. 

4.5.Backup the current /etc/snmp/userDefinedSettings.conf file: 
[Expert@HostName]# cp  /etc/snmp/userDefinedSettings.conf  /etc/snmp/userDefinedSettings.conf_ORIGINAL 

4.6.Edit the current /etc/snmp/userDefinedSettings.conf file: 
[Expert@HostName]# vi  /etc/snmp/userDefinedSettings.conf 

4.7.Define an SNMPv3 user by using the 'createUser' directive, followed by the 'rwuser' directive. 
General syntax:

createUser username (MD5|SHA) authpassphrase [DES|AES] [privpassphrase]

rwuser [-s SECMODEL] USER [noauth|auth|priv [OID | -V VIEW [CONTEXT]]]

Notes for 'createUser' directive:

'createUser' directive creates an SNMPv3 user. 
MD5 and SHA are the authentication types to use. 
DES and AES are the privacy protocols to use. 
If the privacy 'privpassphrase' is not specified, it is assumed to be the same as the authentication 'authpassphrase'. 
Warning: the minimum pass phrase length is 8 characters. 
Notes for 'rwuser' directive:

'rwuser' directive allows read-write (GET, GETNEXT and SET) access for an SNMPv3 user (by default, this will provide access to the full OID tree for authenticated (including encrypted) SNMPv3 requests, using the default context). 
'noauth' allows unauthenticated requests. 
'auth' allows only authenticated requests. 
'priv' enforces the use of encryption. 
The 'OID' field restricts access for that user to the subtree rooted at the given OID. 
The 'VIEW' field restricts access for that user to the subtree rooted at the given named view. 
Example:

createUser test_user SHA pass1234
rwuser test_user

4.8.Log in to Clish. 

4.9.Start the SNMP Agent from Clish: 
HostName> set snmp agent on
HostName> save config 

4.10.Log in to Expert mode. 

4.11.Test the new SNMPv3 user: 
[Expert@HostName]# snmpget -v 3 -u <username> -n "" -l authNoPriv -a SHA -A <password> localhost sysUpTime.0 
Example:
[Expert@HostName]# snmpget -v 3 -u test_user -n "" -l authNoPriv -a SHA -A pass1234 localhost sysUpTime.0

5. Restart your snmp daemon:

[Expert@CP-FW]# service snmpd restart
Stopping snmpd: [FAILED]
Starting snmpd: [  OK  ]
[Expert@CP-FW]# service snmpd restart
Stopping snmpd: [  OK  ]
Starting snmpd: [  OK  ]

-----------------------------------------------------------------------------------------------------------
For SPLAT OS, please refer following post:



[Expert@FW]# snmp user del public [Expert@FW]# snmp user add authuser Nagios pass complexpassphrase priv privatepass [Expert@FW]# snmp service enable
[Expert@FW]# cat /etc/snmp/snmpd.conf
master agentx
syslocation "GDAI"
syscontact CIT32-Security
sysservices 76
rocommunity Snmp3166*
trap2sink 10.94.200.23 Snmp3166*
cp_cleartrap 10 2
proc syslogd 1 1
disk /var 20%
cp_monitor 1.3.6.1.2.1.2.2.1.8.1 == 2 60 "link 1 down"
cp_monitor prErrorFlag.1 != "0" 60 "process monitor"
cp_monitor dskErrorFlag.1 != 0 60 "disk monitor"
cp_monitor 1.3.6.1.4.1.2021.10.1.5.1 > 100 60 "CPU load 1 min"
cp_monitor 1.3.6.1.4.1.2021.10.1.5.2 > 90 60 "CPU load 5 min"
cp_monitor 1.3.6.1.4.1.2021.4.4.0 < 2000 60 "memAvailSwap"
cp_monitor 1.3.6.1.4.1.2021.4.6.0 < 2000 60 "memAvailReal"
cp_monitor 1.3.6.1.4.1.2620.1.5.6.0 != "active" 20 "Cluster State"
cp_monitor 1.3.6.1.4.1.2620.1.1.25.3.0 > 50000 20 "Firewall connections"
cp_monitor 1.3.6.1.2.1.25.2.3.1.6.6 > 60000 60 "/opt hrStorageUsed"
smuxpeer 1.3.6.1.4.1.4.3.1.4
exec maxconn /bin/sh /home/admin/getMaxConn.sh


Activate Check Point MIB with cpconfig :
2.SNMP Extension

There should be 2 processes running: 
 /usr/sbin/snmpd  /opt/CPshrd-R75.40/bin/cpsnmpd
Wanna get the current number of connections in real time?
[Expert@FW]# cat getMaxConn.sh #!/bin/sh /bin/cpfw_start ctl pstat | grep 'Concurrent Connections:' | sed 's/.*out of\ \([0-9]\+\).*/\1/g'

By the way to avoid snmp spam messages in /var/log/messages: Dec 7 15:50:48 hostname snmpd[2621]: Received SNMP packet(s) from UDP: [10.22.1.2]:34665

Follow this SK: Disable verbose SNMP logging - "snmpd[PID]: Received SNMP packet(s) from UDP:" Solution ID:            sk59023