SNMP Traps

This section describes the SNMP traps used on the switch.

Introduction

The switch supports a number of traps that indicate alarm or condition changes on the device. This section will list out those traps and describe how they are generated.

General SNMP configuration for TRAP Generation

The following is applicable for all traps.

iS5Comm# configure terminal

iS5Comm(config)# enable SnmpAgent

iS5Comm(config)# snmp user snmpv3 auth md5 AUTHPASSWD

iS5Comm(config)# snmp community index index3 name testv3 security snmpv3

iS5Comm(config)# snmp group testv3 user snmpv3 security-model v3 nonvolatile

iS5Comm(config)# snmp access testv3 v3 auth read iso write iso notify iso

iS5Comm(config)# snmp targetaddr ht8 param pa8 5.0.0.5 taglist tg8

iS5Comm(config)# snmp targetparams pa8 user snmpv3 security-model v3 auth message-processing v3

iS5Comm(config)# snmp notify testv3 tag tg8 type Trap

Note:

Commands to enable the alarm traps

iS5Comm(config)# alarm config-type switch relay enable

iS5Comm(config)# alarm config-type switch LED enable

iS5Comm(config)# alarm config-type chassis relay enable

iS5Comm(config)# alarm config-type chassis LED enable

iS5Comm(config)# alarm config-type protocol relay enable

iS5Comm(config)# alarm config-type protocol LED enable

iS5Comm(config)# alarm config-type service relay enable

iS5Comm(config)# alarm config-type service LED enable

Note:

Commands to enable the authentication failure trap

iS5Comm(config)# snmp engineId 80.00.08.1c.04.46.54

iS5Comm(config)# snmp user proxyuser1

iS5Comm(config)# snmp group proxygroup user proxyuser1 security-model v2c

iS5Comm(config)# snmp access proxygroup v2c read getview write getview

iS5Comm(config)# snmp view getview 1 mask 1 included volatile

iS5Comm(config)# snmp community index COMM2 name COMM2 security proxyuser1 contextengineid 80.00.08.1c.04.46.54

iS5Comm(config)# exit

iS5Comm#

Note:

IP address 5.0.0.5, as used above, is the IP through which the SNMP manager could be reached. This IP address is being used as an example only.

Line Module Trap

A line module TRAP will be generated, whenever a line module is inserted or removed. Below are the corresponding MIB IDs that would be mentioned in the generated TRAP.

lineModuleNo - 1.3.6.1.4.1.41094.0.250.27.3.6
lmInsertStatus - 1.3.6.1.4.1.41094.0.250.27.3.7

Steps to Generate the Line Module Trap

To generate TRAP for Line Module Removal Event, remove a line module.
To generate TRAP for Line Module Insertion Even, insert the removed line module.

Packet Capture

1.3.6.1.2.1.1.3.0: 16600 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 16600 ---> Total System UP Time in ticks

1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.4.1.41094.0.250.27.3.6 (iso.3.6.1.4.1.41094.0.250.27.3.6)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.4.1.41094.0.250.27.3.6 (iso.3.6.1.4.1.41094.0.250.27.3.6) -> Line module trap OID

1.3.6.1.4.1.41094.0.250.27.3.6: ---> Line module Trap OID
- Object Name: 1.3.6.1.4.1.41094.0.250.27.3.6 (iso.3.6.1.4.1.41094.0.250.27.3.6)
- Value (Integer32): 1 -> Line module ID

1.3.6.1.4.1.41094.0.250.27.3.7: --> Line module connect Status
- Object Name: 1.3.6.1.4.1.41094.0.250.27.3.7 (iso.3.6.1.4.1.41094.0.250.27.3.7)
- Value (Integer32): 2 ---> Connect Status as UP (1) or DOWN (2)

1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Warm Start

The Warm Start TRAP will be generated, when “reload” command is issued. Below is the corresponding MIB ID that would be mentioned, with the TRAP generated.

issWarmStart - 1.3.6.1.4.1.41094.0.250.2.120.11

Steps to generate the Warm Start trap

Execute “reload” command

Packet Capture

1.3.6.1.2.1.1.3.0: 54887 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 54887 ---> Total System UP Time in ticks
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.4.1.41094.0.250.2.120.11 (iso.3.6.1.4.1.41094.0.250.2.120.11)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.4.1.41094.0.250.2.120.11 (iso.3.6.1.4.1.41094.0.250.2.120.11) --> Warm start MIB OID
1.3.6.1.4.1.41094.0.250.2.120.11: --> Warm start MIB OID
- Object Name: 1.3.6.1.4.1.41094.0.250.2.120.11 (iso.3.6.1.4.1.41094.0.250.2.120.11)
- Value (Integer32): 1
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Alarm Trap

An Alarm TRAP will be generated, whenever any kind of alarm is generated. Here we validated the alarm module trap, with alarm generation for LINK UP and LINK DOWN event. Below are the corresponding MIB IDs that would be mentioned, with the TRAP generated.

alarmTraps - 1.3.6.1.4.1.41094.0.250.258.3.1
alarmId - 1.3.6.1.4.1.41094.0.250.258.2.1.1.2
alarmDesc - 1.3.6.1.4.1.41094.0.250.258.2.1.1.4
alarmTimeStr - 1.3.6.1.4.1.41094.0.250.258.2.1.1.5
alarmPriority - 1.3.6.1.4.1.41094.0.250.258.2.1.1.6
alarmGenModule - 1.3.6.1.4.1.41094.0.250.258.2.1.1.7

Steps to generate the Alarm trap

Bring up an interface to generate the LINK UP event
Bring down an interface to generate the LINK DOWN event

Packet Capture

1.3.6.1.2.1.1.3.0: 43567 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 43567 ---> Total System UP Time in ticks
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.4.1.41094.0.250.258.3.1 (iso.3.6.1.4.1.41094.0.250.258.3.1)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.4.1.41094.0.250.258.3.1 (iso.3.6.1.4.1.41094.0.250.258.3.1) -> alarmTraps MIB OID
1.3.6.1.4.1.41094.0.250.258.2.1.1.2: --> alarmId
- Object Name: 1.3.6.1.4.1.41094.0.250.258.2.1.1.2 (iso.3.6.1.4.1.41094.0.250.258.2.1.1.2)
- Value (Integer32): 3000
1.3.6.1.4.1.41094.0.250.258.2.1.1.4:4769302f3920496e74657266616365204c696e6b20537461...
- Object Name: 1.3.6.1.4.1.41094.0.250.258.2.1.1.4 (iso.3.6.1.4.1.41094.0.250.258.2.1.1.4) ---> alarmDesc
- Value (OctetString): 4769302f3920496e74657266616365204c696e6b20537461...
1.3.6.1.4.1.41094.0.250.258.2.1.1.5: --> alarmTimeStr 4170722f31382f32333a33363a3533200000000000000000
- Object Name: 1.3.6.1.4.1.41094.0.250.258.2.1.1.5 (iso.3.6.1.4.1.41094.0.250.258.2.1.1.5)
- Value (OctetString): 4170722f31382f32333a33363a3533200000000000000000
1.3.6.1.4.1.41094.0.250.258.2.1.1.6: --> alarmPriority
- Object Name: 1.3.6.1.4.1.41094.0.250.258.2.1.1.6 (iso.3.6.1.4.1.41094.0.250.258.2.1.1.6)
- Value (Integer32): 2
1.3.6.1.4.1.41094.0.250.258.2.1.1.7: --> alarmGenModule
- Object Name: 1.3.6.1.4.1.41094.0.250.258.2.1.1.7 (iso.3.6.1.4.1.41094.0.250.258.2.1.1.7)
- Value (Integer32): 2
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Power Supply Trap

The Power supply TRAP will be generated, whenever a Power module is inserted or removed.Below are the corresponding MIB IDs that would be mentioned, with the TRAP generated.

issTrapPowerSupply - 1.3.6.1.4.1.41094.0.250.2.120.6
issPowerSupplyPresence - 1.3.6.1.4.1.41094.0.250.2.121.132
issPowerSupplyActive - 1.3.6.1.4.1.41094.0.250.2.121.133

Steps to generate the Power Supply trap

Remove a power module to generate POWER module removal event
Insert a power module to generate POWER module insertion event

Packet Capture

1.3.6.1.2.1.1.3.0: 129754 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 129754 ---> Total System UP Time in ticks
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.4.1.41094.0.250.2.120.6 (iso.3.6.1.4.1.41094.0.250.2.120.6)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.4.1.41094.0.250.2.120.6 (iso.3.6.1.4.1.41094.0.250.2.120.6) --> issTrapPowerSupply
1.3.6.1.4.1.41094.0.250.2.121.132: ---> issPowerSupplyPresence
- Object Name: 1.3.6.1.4.1.41094.0.250.2.121.132 (iso.3.6.1.4.1.41094.0.250.2.121.132)
- Value (Integer32): 0
1.3.6.1.4.1.41094.0.250.2.121.133: ---> issPowerSupplyActive
- Object Name: 1.3.6.1.4.1.41094.0.250.2.121.133 (iso.3.6.1.4.1.41094.0.250.2.121.133)
- Value (Integer32): 0
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Cold Start Trap

The Cold Start TRAP will be generated, whenever the image is reloaded after doing SNMP configurations for TRAP and “write-startup” is done. Below is the corresponding MIB ID that would be mentioned, with the TRAP generated.

coldStart - 1.3.6.1.6.3.1.1.5.1

Steps to generate the Cold Start trap

Execute “reload” command

Packet Capture

1.3.6.1.2.1.1.3.0: 1419 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 1419 ---> Total System UP Time in ticks
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.6.3.1.1.5.1 (iso.3.6.1.6.3.1.1.5.1)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.6.3.1.1.5.1 (iso.3.6.1.6.3.1.1.5.1) ---> coldStart MIB OID
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Authentication Failure Trap

An Authentication failure TRAP will be generated, whenever the SNMP connectivity cannot be established due to Authentication failures. Below is the corresponding MIB ID that would be mentioned, with the TRAP generated.

authenticationFailure - 1.3.6.1.6.3.1.1.5.5

Steps to generate the Authentication trap

Execute below command to enable Authentication trap
- ```
snmp-server enable traps snmp authentication
```
Execute below command from linux, to invoke error in authentication
- ```
snmpwalk -c COMM1 -v2c 7.0.0.1 iso
```

Note:

Here the community name configured is COMM2, but from LINUX, we are trying to authenticate with COMM1, which would cause a authentication failure.

Packet Capture

1.3.6.1.2.1.1.3.0: 1419 ---> sysUpTime
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 1419 ---> Total System UP Time in ticks
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.6.3.1.1.5.5 (iso.3.6.1.6.3.1.1.5.5)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.6.3.1.1.5.5 (iso.3.6.1.6.3.1.1.5.5) --> authenticationFailure OID
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Link UP / DOWN Trap

A LINK UP / LINK DOWN TRAP will be generated, whenever any interface is brought UP or DOWN. Below is the corresponding MIB ID that would be mentioned, with the TRAP generated.

linkUp - 1.3.6.1.6.3.1.1.5.4
linkDown - 1.3.6.1.6.3.1.1.5.3
ifIndex - 1.3.6.1.2.1.2.2.1.1.<ifindex>
ifAdminStatus - 1.3.6.1.2.1.2.2.1.7.<ifIndex
ifOperStatus - 1.3.6.1.2.1.2.2.1.8.<ifIndex>

Steps to generate the Link UP/DOWN trap

Bring DOWN an active interface through command “shutdown”
Bring UP the same interface through command “no shutdown”

Packet Capture (for link UP)

1.3.6.1.2.1.1.3.0: 136427
- Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
- Value (Timeticks): 136427
1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.6.3.1.1.5.4 (iso.3.6.1.6.3.1.1.5.4)
- Object Name: 1.3.6.1.6.3.1.1.4.1.0 (iso.3.6.1.6.3.1.1.4.1.0) --> snmpTrap OID
- Value (OID): 1.3.6.1.6.3.1.1.5.4 (iso.3.6.1.6.3.1.1.5.4) --> linkup MIB OID
1.3.6.1.2.1.2.2.1.1.9: --> ifIndex MIB OID
- Object Name: 1.3.6.1.2.1.2.2.1.1.9 (iso.3.6.1.2.1.2.2.1.1.9)
- Value (Integer32): 9
1.3.6.1.2.1.2.2.1.7.9: --> ifAdminStatus MIB OID
- Object Name: 1.3.6.1.2.1.2.2.1.7.9 (iso.3.6.1.2.1.2.2.1.7.9)
- Value (Integer32): 1
1.3.6.1.2.1.2.2.1.8.9: --> ifOperStatus MIB OID
- Object Name: 1.3.6.1.2.1.2.2.1.8.9 (iso.3.6.1.2.1.2.2.1.8.9)
- Value (Integer32): 1
1.3.6.1.6.3.1.1.4.3.0: 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) --> snmpTrapEnterprise
- Object Name: 1.3.6.1.6.3.1.1.4.3.0 (iso.3.6.1.6.3.1.1.4.3.0)
- Value (OID): 1.3.6.1.2.1.11 (iso.3.6.1.2.1.11) ---> snmp OID

Spanning Tree Trap

The Spanning tree topology change trap is generated whenever we shut / no shut a port, change the priority of any bridge to invoke new root selection, new port role selection, etc.

Steps to generate the Spanning Tree trap

Change spanning priority to invoke New ROOT bridge selection
Bring DOWN an active interface through command “shutdown”
Bring UP the same interface through command “no shutdown”

Packet Capture

Below are the MIBs that will be mentioned for different kind of traps from PVRST.

fsPvrstTopologyChgTrap - 1.3.6.1.4.1.41094.0.250.161.3.0.4
fsPvrstBrgAddress - 1.3.6.1.4.1.41094.0.250.161.1.4
fsPvrstInstTopChanges - 1.3.6.1.4.1.41094.0.250.161.1.14.1.11
fsFuturePvrstTraps - 1.3.6.1.4.1.41094.0.250.161.3
fsPvrstNewRootTrap - 1.3.6.1.4.1.41094.0.250.161.3.0.3
fsPvrstInstDesignatedRoot - 1.3.6.1.4.1.41094.0.250.161.1.14.1.16
fsPvrstNewPortRoleTrap - 1.3.6.1.4.1.41094.0.250.161.3.0.7
fsPvrstOldRoleType - 1.3.6.1.4.1.41094.0.250.161.2.5.1.2
fsPvrstPortRoleType - 1.3.6.1.4.1.41094.0.250.161.2.5.1.1

data: sNMPv2-Trap (7)
- sNMPv2-Trap
  - request-id: 1436813334
  - error-status: noError (0)
  - error-index: 0
  - variable-bindings: 5 items

Item #1

name: 1.3.6.1.2.1.1.3.0 (SNMPv2-MIB::sysUpTime.0)
valueType: value (0)
- value: simple (4294967295)
- value: simple (4294967295)
  - application-wide: timeticks-value (3): timeticks-value: 1120239

Item #2

name: 1.3.6.1.6.3.1.1.4.1.0 (SNMPv2-MIB::snmpTrapOID.0)
valueType: value (0)
- value: simple (4294967295)
  - simple: objectID-value (2): Value: OID: SNMPv2-SMI::enterprises.41094.0.250.161.3.0.4

Item #3

name: 1.3.6.1.4.1.41094.0.250.161.1.4 (SNMPv2-SMI::enterprises.41094.0.250.161.1.4)
valueType: value (0)
- value: simple (4294967295)
  - simple: string-value (1): Value: Hex-STRING: E8 E8 75 90 2B 01

Item #4

name: 1.3.6.1.4.1.41094.0.250.161.1.14.1.11.1 (SNMPv2-SMI::enterprises.41094.0.250.161.1.14.1.11.1)
valueType: value (0)
- value: simple (4294967295)
  - simple: integer-value (0): Value: INTEGER: 6

Item #5

name: 1.3.6.1.6.3.1.1.4.3.0 (SNMPv2-MIB::snmpTrapEnterprise.0)
valueType: value (0)
- value: simple (4294967295)
  - simple: objectID-value (2): Value: OID: SNMPv2-SMI::enterprises.41094.0.250.161.3

Temperature Trap

The temperature trap will be generated whenever the temperature of the hardware exceeds the High threshold limit or falls lesser than the minimum threshold limit. Below is the corresponding MIB ID that would be mentioned, with the TRAP generated.

issTrapTemperature - 1.3.6.1.4.1.41094.0.250.2.120.4
issSwitchMinThresholdTemperature - 1.3.6.1.4.1.41094.0.250.2.121.64
issSwitchMaxThresholdTemperature - 1.3.6.1.4.1.41094.0.250.2.121.65
issSwitchCurrentTemperature - 1.3.6.1.4.1.41094.0.250.2.121.66

Steps to generate the Temperature trap

Check the current temperature of the hardware using command “show env all”
Set the Max temperature threshold limit as lesser than the current temperature, to generate trap, using the below command.
```
set switch temperature max threshold <value>
```

Packet Capture

data: sNMPv2-Trap (7)
- sNMPv2-Trap
  - request-id: 1821105562
  - error-status: noError (0)
  - error-index: 0
  - variable-bindings: 5 items

Item #1

name: 1.3.6.1.2.1.1.3.0 (SNMPv2-MIB::sysUpTime.0)
valueType: value (0)
- value: simple (4294967295)
- value: simple (4294967295)
  - application-wide: timeticks-value (3):timeticks-value: 7814

Item #2

name: 1.3.6.1.6.3.1.1.4.1.0 (SNMPv2-MIB::snmpTrapOID.0)
valueType: value (0)
- value: simple (4294967295): simple: objectID-value (2)
  - Value: OID: SNMPv2-SMI::enterprises.41094.0.250.2.120.4 ---> issTrapTemperature

Item #3

name: 1.3.6.1.4.1.41094.0.250.2.121.64 (SNMPv2-SMI::enterprises.41094.0.250.2.121.64) ---> issSwitchMinThresholdTemperature
valueType: value (0)
- value: simple (4294967295):simple: integer-value (0)
  - Value: INTEGER: -35

Item #4

name: 1.3.6.1.4.1.41094.0.250.2.121.65 (SNMPv2-SMI::enterprises.41094.0.250.2.121.65) ---> issSwitchMaxThresholdTemperature
valueType: value (0)
- value: simple (4294967295):simple: integer-value (0)
  - Value: INTEGER: 40

Item #5

name: 1.3.6.1.4.1.41094.0.250.2.121.66 (SNMPv2-SMI::enterprises.41094.0.250.2.121.66) ---> issSwitchCurrentTemperature
valueType: value (0)
- value: simple (4294967295):simple: integer-value (0)
  - Value: INTEGER: 41

Port Security Traps

Item #1

ifSwitchPortSecRecoveryStatus OBJECT-TYPE
- SYNTAX INTEGER { automatic(1), manual(2) }
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - specifies the recovery mode for the ports in the system, when port-violation mode configured with shut-down. The value 1 indicates authomatic, the port will bring-up after the user configured time or the default time. The value 2 indicates manual, The users have to do no shutdown to bring up the port.
- DEFVAL { manual }
- ::= { if 37 }

Item #2

ifSwitchPortSecRecoveryTime OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - The value indicates the the recovery time for a port, from shut-down state that occurred due to a port-security violation, to up-state, upon the mode configured as automatic in ifSwitchPortSecRecoveryStatus
- DEFVAL { 5 }
- ::= { if 38 }

Item #3

dot1qFutureVlanPortUnicastMacLimitStatus OBJECT-TYPE
- SYNTAX EnabledStatus
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - A truth value indicating the unicast MAC limit learning enabled/disabled status for this port
- DEFVAL { enabled }
- ::= { dot1qFutureVlanPortEntry 17 }

Item #4

dot1qFutureVlanPortUnicastMacLimit OBJECT-TYPE
- SYNTAX Unsigned32 (0..3000)
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - The limiting value on the number of distinct unicast MAC addresses learnt in a VLAN. The lower limit and upper limit value that can be SET for this object is determined by the underlying hardware.
- ::= { dot1qFutureVlanPortEntry 18 }

Item #5

dot1qFutureVlanPortSecureStatus OBJECT-TYPE
- SYNTAX EnabledStatus
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - A truth value indicating the port-security status enabled/disabled status for this port. When port security is disabled, trusted MAC settings and MAC learn limit settings are not applicable.
- DEFVAL { disabled }
- ::= { dot1qFutureVlanPortEntry 19 }

Item #6

dot1qFutureSwitchPortSecViolationTrap NOTIFICATION-TYPE
- OBJECTS { dot1qFutureVlanPort }
- STATUS current
- DESCRIPTION
- - This trap is generated when Port security is enabled on the port and violation occurred for a configured number of times
- ::= { dot1qVlanTraps 4 }

Item #7

MIB for Trap-syslog status configuration
- dot1qFutureVlanPortSecTrapSyslogStatus OBJECT-TYPE
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - A truth value indicating the trap and syslog status for port-security violation is enabled, and so traps and syslog will be generated when violations occur. When this status for port-secuirty violation is disabled, traps and syslogs will not be sent upon violation.
- DEFVAL { disabled }
- ::= { dot1qFutureVlan 10 }

Item #8

MIB for Trap, syslog rate configuration
- dot1qFutureVlanPortSecTrapSyslogRate OBJECT-TYPE
- SYNTAX Integer32 (1..10)
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- - TrapSyslog rate is the value, for the Max no. of Traps and Syslog that could be sent in a second, with violation events. The range of trap syslog rate could be configured is from 1 to 10
- ::= { dot1qFutureVlan 11 }