Added Brocade VDX Mibs

This commit is contained in:
xavier.beaudouin 2016-03-30 16:47:13 +02:00
parent c43970edff
commit 10959a1049
17 changed files with 6464 additions and 85 deletions

View File

@ -0,0 +1,60 @@
-- *********************************************************************
-- BROCADE-IEEE8021-PAE-CAPABILITY-MIB.mib:
-- IEEE8021-PAE-MIB AGENT-CAPABILITIES
--
-- June 2012, Balachandar Mani
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
-- *********************************************************************
BROCADE-IEEE8021-PAE-CAPABILITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
brocadeAgentCapability
FROM Brocade-REG-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF
MODULE-IDENTITY
FROM SNMPv2-SMI;
brocadeIeee8021PaeCapability MODULE-IDENTITY
LAST-UPDATED "201206010000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO
"Customer Support Group
Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION
"Agent capabilities for IEEE8021-PAE-MIB implementation."
REVISION "201206010000Z"
DESCRIPTION
"The initial version of this MIB module."
::= { brocadeAgentCapability 1 }
--
-- Agent capability for NOS 3.0.0 (VDX Platform)
--
brocadeIeee8021PaeVdx300R1 AGENT-CAPABILITIES
PRODUCT-RELEASE "NOS3.0.0"
STATUS current
DESCRIPTION "IEEE8021-PAE-MIB capabilities."
SUPPORTS IEEE8021-PAE-MIB
INCLUDES {
dot1xPaeSystemGroup,
dot1xPaeAuthConfigGroup,
dot1xPaeAuthStatsGroup,
dot1xPaeAuthDiagGroup,
dot1xPaeAuthSessionStatsGroup,
dot1xPaeAuthConfigGroup2
}
::= { brocadeIeee8021PaeCapability 1 }
END

View File

@ -0,0 +1,59 @@
-- *********************************************************************
-- BROCADE-IEEE8023-LAG-CAPABILITY-MIB.mib:
-- IEEE8023-LAG-MIB AGENT-CAPABILITIES
--
-- June 2012, Balachandar Mani
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
-- *********************************************************************
BROCADE-IEEE8023-LAG-CAPABILITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
brocadeAgentCapability
FROM Brocade-REG-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF
MODULE-IDENTITY
FROM SNMPv2-SMI;
brocadeIeee8023LagCapability MODULE-IDENTITY
LAST-UPDATED "201206060000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO
"Customer Support Group
Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION
"Agent capabilities for IEEE8023-LAG-MIB implementation."
REVISION "201206060000Z"
DESCRIPTION
"The initial version of this MIB module."
::= { brocadeAgentCapability 3 }
--
-- Agent capability for NOS 3.0.0 (VDX Platform)
--
brocadeIeee8023LagVdx300R1 AGENT-CAPABILITIES
PRODUCT-RELEASE "NOS3.0.0"
STATUS current
DESCRIPTION "IEEE8023-LAG-MIB capabilities."
SUPPORTS IEEE8023-LAG-MIB
INCLUDES {
dot3adAggGroup,
dot3adAggPortListGroup,
dot3adAggPortGroup,
dot3adAggPortStatsGroup,
dot3adTablesLastChangedGroup
}
::= { brocadeIeee8023LagCapability 1 }
END

View File

@ -0,0 +1,64 @@
-- *********************************************************************
-- BROCADE-LLDP-CAPABILITY-MIB.mib: LLDP-MIB AGENT-CAPABILITIES
--
-- June 2012, Chakraborty Debojyoti
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
-- *********************************************************************
BROCADE-LLDP-CAPABILITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
brocadeAgentCapability
FROM Brocade-REG-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF
MODULE-IDENTITY
FROM SNMPv2-SMI;
brocadeLLDPCapability MODULE-IDENTITY
LAST-UPDATED "201206060000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO
"Customer Support Group
Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION
"Agent capabilities for LLDP-MIB implementation."
REVISION "201206060000Z"
DESCRIPTION
"The initial version of this MIB module."
::= { brocadeAgentCapability 1 }
--
-- Agent capability for NOS 3.0.0 (VDX Platform)
--
brocadeLLDPVdx300R1 AGENT-CAPABILITIES
PRODUCT-RELEASE "NOS3.0.0"
STATUS current
DESCRIPTION "LLDP-MIB capabilities."
SUPPORTS LLDP-MIB
INCLUDES {
lldpConfigGroup,
lldpConfigRxGroup,
lldpConfigTxGroup,
lldpStatsRxGroup,
lldpStatsTxGroup,
lldpLocSysGroup,
lldpRemSysGroup
}
VARIATION lldpConfigManAddrPortsTxEnable
ACCESS not-implemented
DESCRIPTION "Not Supported."
::= { brocadeLLDPCapability 1 }
END

View File

@ -0,0 +1,105 @@
-- *********************************************************************
-- BROCADE-LLDP-EXT-DOT3-CAPABILITY-MIB.mib:
-- LLDP-EXT-DOT3-MIB AGENT-CAPABILITIES
--
-- June 2012, Chakraborty Debojyoti
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
-- *********************************************************************
BROCADE-LLDP-EXT-DOT3-CAPABILITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
brocadeAgentCapability
FROM Brocade-REG-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF
MODULE-IDENTITY
FROM SNMPv2-SMI;
brocadeLLDP-EXT-DOT3Capability MODULE-IDENTITY
LAST-UPDATED "201206060000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO
"Customer Support Group
Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION
"Agent capabilities for LLDP-EXT-DOT3-MIB implementation."
REVISION "201206060000Z"
DESCRIPTION
"The initial version of this MIB module."
::= { brocadeAgentCapability 2 }
--
-- Agent capability for NOS 3.0.0 (VDX Platform)
--
brocadeLLDP-EXT-DOT3Vdx300R1 AGENT-CAPABILITIES
PRODUCT-RELEASE "NOS3.0.0"
STATUS current
DESCRIPTION "LLDP-EXT-DOT3-MIB capabilities."
SUPPORTS LLDP-EXT-DOT3-MIB
INCLUDES {
lldpXdot3ConfigGroup,
lldpXdot3LocSysGroup,
lldpXdot3RemSysGroup
}
VARIATION lldpXdot3LocPowerPortClass
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3LocPowerMDISupported
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3LocPowerMDIEnabled
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3LocPowerPairControlable
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3LocPowerPairs
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3LocPowerClass
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerPortClass
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerMDISupported
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerMDIEnabled
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerPairControlable
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerPairs
ACCESS not-implemented
DESCRIPTION "Not Supported."
VARIATION lldpXdot3RemPowerClass
ACCESS not-implemented
DESCRIPTION "Not Supported."
::= { brocadeLLDP-EXT-DOT3Capability 1 }
END

242
mibs/BROCADE-MAPS-MIB Normal file
View File

@ -0,0 +1,242 @@
-- *********************************************************************
-- BROCADE-PRODUCTS-MIB.mib: Brocade Products MIB.
--
-- Dec 2014, Prabhu Sundaram
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
--
-- *********************************************************************
BROCADE-MAPS-MIB DEFINITIONS ::= BEGIN
IMPORTS
Integer32, OBJECT-IDENTITY, OBJECT-TYPE,
MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
bcsiModules
FROM Brocade-REG-MIB
swVfId
FROM SYSTEM-MIB;
maps MODULE-IDENTITY
LAST-UPDATED "201304221330Z" -- April 22, 2013 1:30pm
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
120 Holger Way,
San Jose, CA 95134 U.S.A
Tel: +1-408-392-6061
Fax: +1-408-392-6656
Email: support@Brocade.COM
WEB: www.brocade.com"
DESCRIPTION "The MIB module is for Brocade's Monitoring and
Alerting Policy Suite[MAPS] feature."
REVISION "201303011400Z" -- March 01, 2013 02:00pm
DESCRIPTION "added db category"
REVISION "201304221330Z" -- April 22, 2013 01:30pm
DESCRIPTION "Updated mapsConfigObjectGroupType syntax values"
REVISION "201501131400Z" -- January 13, 2015 02:00pm
DESCRIPTION "modified SW-MIB from IMPORTS to SYSTEM-MIB"
REVISION "201501131400Z" -- June 10, 2015 02:00pm
DESCRIPTION "Updated mapsConfigObjectGroupType enum value"
::= { bcsiModules 4 }
mapsTraps OBJECT-IDENTITY
STATUS current
DESCRIPTION "The OID represents the MAPS Trap."
::= { maps 0 }
mapsConfig OBJECT-IDENTITY
STATUS current
DESCRIPTION "The OID represents the MAPS Config params."
::= { maps 1 }
mapsConfigRuleName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (64))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the rule name which associates a condition
with actions that need to be triggered
when the specified condition is evaluated to true."
::= { mapsConfig 1 }
mapsConfigCondition OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (64))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the condition defined in the rule.
It includes the counter, time base and threshold
value with the logical operation (eg: >, <, >= etc) that
needs to be evaluated. Eg: (CRC/MIN > 10)"
::= { mapsConfig 2 }
mapsConfigNumOfMS OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the number of monitoring system entries
in the notifications"
::= { mapsConfig 3 }
mapsConfigMsName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This is monitoring system name like CRC, ITW, PS, FAN."
::= { mapsConfig 4 }
mapsConfigObjectGroupType OBJECT-TYPE
SYNTAX INTEGER {
unknown (1),
ps (2),
fan (3),
port (4),
ve-port-cir (5),
ts (6),
slot (7),
gbic (8),
flash (9),
rule (10),
switch (11),
chassis (12),
cpu (13),
wwn (14),
flow (15),
eth-port (16)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the object group type like circuit, PS, FAN."
::= { mapsConfig 5 }
mapsConfigObjectKeyType OBJECT-TYPE
SYNTAX INTEGER {
int32 (1),
uint32 (2),
float (3),
string (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the object key type. The main purpose of this
object to help NMS applications to interpret the data easily.
Eg: If the mapsConfigObjectGroupType is port then the key type
is an integer and key value is the port number."
::= { mapsConfig 6 }
mapsConfigObjectKeyValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (64))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the object key value. Incase of integer this field
keeps as 1, 2, 3, 4, etc., and for string it keeps
flowname1, flowname2, etc., Eg: if Group type is port,
then the object key value is the port number."
::= { mapsConfig 7 }
mapsConfigValueType OBJECT-TYPE
SYNTAX INTEGER {
int32 (1),
uint32 (2),
float (3),
string (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the value type which could be integer, float
or string. The main purpose of this object to help
NMS applications to interpret the data easily."
::= { mapsConfig 8 }
mapsConfigCurrentValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (64))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the actual value of the monitoring
system."
::= { mapsConfig 9 }
mapsConfigTimeBase OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The time period across which the change
in a counter is to be monitored"
::= { mapsConfig 10 }
mapsConfigSeverityLevel OBJECT-TYPE
SYNTAX INTEGER {
critical (1),
error (2),
warning (3),
informational (4),
debug (5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the severity level of the
condition triggered"
::= { mapsConfig 11 }
mapsConfigMsList OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the list of the monitoring systems. The
format is <msname>,<value-type>,<current-value>,<time-base>
::<msName>,<value-type>,<current-value>,<time-base>::."
::= { mapsConfig 12 }
mapsConfigAction OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It indicates the actions(bitmask value) that need
to be triggered when the specified condition
evaluated to be true. Action bitmask value mapping are
none (0),
raslog (1),
snmp (2),
port-fence (8),
email (16),
switchstatus-down (64),
switchstatus-marginal (128),
switchstatus-healthy (256),
switchpolicy (512),
sfp-marginal (1024)
Ex: mapsConfigAction value 3 represents both raslog and snmp action"
::= { mapsConfig 13 }
mapsDbCategory OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (24))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "indicates db category name"
::= { mapsConfig 14 }
mapsTrapAM NOTIFICATION-TYPE
OBJECTS {
mapsConfigRuleName,
mapsConfigObjectGroupType,
mapsConfigObjectKeyType,
mapsConfigObjectKeyValue,
mapsConfigNumOfMS,
mapsConfigMsList,
mapsConfigSeverityLevel,
mapsConfigCondition,
mapsConfigAction,
swVfId,
mapsDbCategory
}
STATUS current
DESCRIPTION "Trap to be send for MAPS threshold events."
::= { mapsTraps 1 }
END

69
mibs/BROCADE-PRODUCTS-MIB Normal file
View File

@ -0,0 +1,69 @@
-- ****************************************************************
-- BROCADE-PRODUCTS-MIB.my: Brocade Products MIB.
--
-- Feb 2012, Sanjeev C Joshi, Yasar Khan
--
-- Copyright (c) 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
--
-- ****************************************************************
BROCADE-PRODUCTS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
bcsiReg
FROM Brocade-REG-MIB;
brocadeProductsMIB MODULE-IDENTITY
LAST-UPDATED "201202030000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO
"Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION "This MIB module is for defining all the object
identifiers to identify various hardware
platforms. These identifiers are used as value
for 'sysObjectID'."
REVISION "201202030000Z"
DESCRIPTION "Initial version of this MIB module."
REVISION "201311210000Z"
DESCRIPTION "Updated name for Blackbird as vdx2740"
REVISION "201309251300Z"
DESCRIPTION "Added new product name for Draco-T platform."
REVISION "201410071405Z"
DESCRIPTION "Added product name for RIGEL1U as vdx7770P36
and RIGEL2U as vdx7770P72."
REVISION "201508111305Z"
DESCRIPTION "Updated the product name for RIGEL1U as vdx6940Q36.
then added RIGELMOR product name as vdx6940S144 and Removed RIGEL2U platform"
::= { bcsiReg 3 }
brocadeProducts OBJECT IDENTIFIER ::= { brocadeProductsMIB 1 }
vdx6740 OBJECT IDENTIFIER ::= { brocadeProducts 131 }
vdx6740T OBJECT IDENTIFIER ::= { brocadeProducts 137 }
vdx2740 OBJECT IDENTIFIER ::= { brocadeProducts 138 }
vdx6740T1G OBJECT IDENTIFIER ::= { brocadeProducts 151 }
vdx6940Q36 OBJECT IDENTIFIER ::= { brocadeProducts 153 }
vdx6940S144 OBJECT IDENTIFIER ::= { brocadeProducts 164 }
vdx8770S4 OBJECT IDENTIFIER ::= { brocadeProducts 1000 }
vdx8770S8 OBJECT IDENTIFIER ::= { brocadeProducts 1001 }
vdx8770S16 OBJECT IDENTIFIER ::= { brocadeProducts 1002 }
END

352
mibs/BROCADE-VCS-MIB Normal file
View File

@ -0,0 +1,352 @@
BROCADE-VCS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Gauge32,
Counter32, Unsigned32 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
TruthValue, TEXTUAL-CONVENTION,
DisplayString FROM SNMPv2-TC
InetAddress, InetAddressType FROM INET-ADDRESS-MIB
FcWwn FROM Brocade-TC
bcsiModules FROM Brocade-REG-MIB;
brocadeVcsMIB MODULE-IDENTITY
LAST-UPDATED "201504080000Z"
ORGANIZATION
"Brocade Communications Systems Inc."
CONTACT-INFO
"130 Holger Way,
San Jose, CA
95134 USA.
Phone: +1-408-333-8000
Email: vivekk@brocade.com"
DESCRIPTION
"The MIB module for the monitoring of VCS fabrics. VCS
fabrics is a proprietary technology of Brocade.
A VCS fabric consists of a set of inter-connected
Brocade VDX switches. These set of switches together
behave like a single L2 switch to the outside world.
The cluster can operate in 2 modes: fabric mode and
Logical chassis mode.
In fabric mode, the switches together behave like a
single L2 switch - but configuration on each switch
is independent of the other.
In logical chassis mode, one switch in the fabric is
elected as the principal switch. All configurations
need to be done only from the principal switch.
This is synced across to all the switches in the fabric.
Thus the configuration information is the same on all
the switches."
REVISION "201504080000Z"
DESCRIPTION
"Initial version."
::= { bcsiModules 6 }
brocadeVcsMIBObjects OBJECT IDENTIFIER ::= { brocadeVcsMIB 1 }
brocadeVcsMIBConformance OBJECT IDENTIFIER ::= { brocadeVcsMIB 2 }
VcsConfigMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The configuration mode that is in effect in the VCS
fabric.
local(1) - configuration is local to the switch.
distributed(2) - configuration is to be done from the
principal switch and will be the same
across all the switches in the fabric."
SYNTAX INTEGER {
local(1),
distributed(2)
}
VcsOperationMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The operational mode of the fabric.
fabricCluster(1) - the entire set of switches in the
cluster behaves like a single L2
switch to the outer world. However,
configuration is local to each switch.
logicalChassis(2) - in this case the fabric behaves
like a single L2 switch and the
configuration is driven from the
principal switch and is the same
across all switches in the fabric."
SYNTAX INTEGER {
fabricCluster(1),
logicalChassis(2)
}
VcsIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A number that uniquely identifies a fabric. Two different
fabrics would have different identifiers."
SYNTAX Unsigned32 (1 .. 8192)
VcsRbridgeId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A number that uniquely identifies a switch within a fabric."
SYNTAX Unsigned32 (1 .. 239)
VcsClusterCondition ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The state of the fabric as a whole.
good(1) - indicates that all switches are in good
condition and cluster is fine.
degraded(2) - indicates that one or more switches are
offline and cluster has degraded.
error(3) - Internal error state."
SYNTAX INTEGER {
good(1),
degraded(2),
error(3)
}
vcsConfigMode OBJECT-TYPE
SYNTAX VcsConfigMode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration mode of this cluster that is in effect."
::= { brocadeVcsMIBObjects 1 }
vcsModeOfOperation OBJECT-TYPE
SYNTAX VcsOperationMode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational mode of this cluster."
::= { brocadeVcsMIBObjects 2 }
vcsIdentifier OBJECT-TYPE
SYNTAX VcsIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The unique identifier of this cluster."
::= { brocadeVcsMIBObjects 3 }
vcsVirtualIpV4Address OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The virtual IPv4 address of the cluster. Management
stations can use this address to send requests."
::= { brocadeVcsMIBObjects 4 }
vcsVirtualIpV6Address OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The virtual IPv6 address of the cluster. Management
stations can use this address to send requests."
::= { brocadeVcsMIBObjects 5 }
vcsVirtualIpAssociatedRbridgeId OBJECT-TYPE
SYNTAX VcsRbridgeId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rbridge-id of the switch that hosts the virtual IP
address."
::= { brocadeVcsMIBObjects 6 }
vcsVirtualIpInterfaceId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface Id that is configured in the case of
inband configuration. If it is not inband configuration,
then this object will contain the value 0."
::= { brocadeVcsMIBObjects 7 }
vcsVirtualIpV4OperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the virtual IPv4 address."
::= { brocadeVcsMIBObjects 8 }
vcsVirtualIpV6OperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the virtual IPv6 address."
::= { brocadeVcsMIBObjects 9 }
vcsNumNodesInCluster OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of switches in the cluster that are currently
online."
::= { brocadeVcsMIBObjects 10 }
vcsClusterCondition OBJECT-TYPE
SYNTAX VcsClusterCondition
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The condition of the cluster as a whole."
::= { brocadeVcsMIBObjects 11 }
vcsFabricIslTable OBJECT-TYPE
SYNTAX SEQUENCE OF VcsFabricIslEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains all the ISLs (Inter Switch Link) on
the local device."
::= { brocadeVcsMIBObjects 12 }
vcsFabricIslEntry OBJECT-TYPE
SYNTAX VcsFabricIslEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents a single Inter Switch Link (ISL) on this
switch."
INDEX { vcsFabricIslIndex }
::= { vcsFabricIslTable 1 }
VcsFabricIslEntry ::= SEQUENCE {
vcsFabricIslIndex Unsigned32,
vcsFabricIslIntfName DisplayString,
vcsFabricIslNbrIntfName DisplayString,
vcsFabricIslNbrWWN FcWwn,
vcsFabricIslNbrName DisplayString,
vcsFabricIslBW Unsigned32,
vcsFabricIslIsTrunk TruthValue
}
vcsFabricIslIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique id to distinguish this ISL from others on the
local device."
::= { vcsFabricIslEntry 1 }
vcsFabricIslIntfName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface name (ifName) of the interface on which
the ISL is formed on this switch."
::= { vcsFabricIslEntry 2 }
vcsFabricIslNbrIntfName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface name (ifName) of the interface on the
neighboring switch for this ISL."
::= { vcsFabricIslEntry 3 }
vcsFabricIslNbrWWN OBJECT-TYPE
SYNTAX FcWwn
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The World Wide Name (WWN) of the neighboring switch
for this ISL."
::= { vcsFabricIslEntry 4 }
vcsFabricIslNbrName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the neighboring switch on which this ISL
is formed."
::= { vcsFabricIslEntry 5 }
vcsFabricIslBW OBJECT-TYPE
SYNTAX Unsigned32
UNITS "megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The band-width of this ISL."
::= { vcsFabricIslEntry 6 }
vcsFabricIslIsTrunk OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication whether this ISL is a trunk interface.
A value of true(1) means it is a trunk.
A value of false(2) means it is not a trunk."
::= { vcsFabricIslEntry 7 }
-- Conformance information
brocadeVcsConformanceGroups
OBJECT IDENTIFIER ::= { brocadeVcsMIBConformance 1 }
brocadeVcsCompliances
OBJECT IDENTIFIER ::= { brocadeVcsMIBConformance 2 }
-- Compliance statements
brocadeVcsCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance information for this MIB."
MODULE -- this module
MANDATORY-GROUPS { brocadeVcsObjectGroup }
::= { brocadeVcsCompliances 1 }
-- units of conformance
brocadeVcsObjectsGroup OBJECT-GROUP
OBJECTS { vcsConfigMode,
vcsModeOfOperation,
vcsIdentifier,
vcsVirtualIpV4Address,
vcsVirtualIpV6Address,
vcsVirtualIpAssociatedRbridgeId,
vcsVirtualIpInterfaceId,
vcsVirtualIpV4OperStatus,
vcsVirtualIpV6OperStatus,
vcsNumNodesInCluster,
vcsClusterCondition,
vcsFabricIslIndex,
vcsFabricIslIntfName,
vcsFabricIslNbrIntfName,
vcsFabricIslNbrWWN,
vcsFabricIslNbrName,
vcsFabricIslBW,
vcsFabricIslIsTrunk
}
STATUS current
DESCRIPTION
"The MIB objects related to VCS monitoring."
::= { brocadeVcsConformanceGroups 1 }
END

View File

@ -1,85 +1,80 @@
--
-- Title: Brocade Registration MIB, Version v5.0
--
-- This is specified based on SMIv2, mainly to ensure that the specification
-- can be parsed easily by off-the-shelf network management product in
-- the market.
--
-- The goal of this mib is to access all the Brocade Enterprise products.
-- This mib file contains the generic textual conventions of Brocade's product.
--
Brocade-REG-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI;
-- bcsiGlobalRegModule MODULE-IDENTITY
-- LAST-UPDATED "0210030000Z"
-- ORGANIZATION "Brocade Communications Systems, Inc.,"
-- CONTACT-INFO "Customer Support Group
-- Brocade Communications Systems,
-- 1745 Technology Drive,
-- San Jose, CA 95110 U.S.A
-- Tel: +1-408-392-6061
-- Fax: +1-408-392-6656
-- Email: support@Brocade.COM
-- WEB: www.brocade.com"
--
--
-- DESCRIPTION "The MIB module is for Brocade's Central Repository of
-- all OIDs for an enterprise. Thus any group within Brocade
-- looking to add a new product specific MIB need only look
-- at Brocade tree for the new MIB module.
-- Copyright (c) 1996-2002 Brocade Communications Systems, Inc.
-- All rights reserved."
-- REVISION "0301131430Z" Jan 13, 2003 2:30pm
-- DESCRIPTION "The initial version of this module."
-- ::= { bcsiModules 1 }
bcsi OBJECT IDENTIFIER ::= { enterprises 1588 }
-- bcsi OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The Root of the OID sub-tree assigned to Brocade by
-- the Internet Assigned Numbers Authority (IANA)."
-- ::= { enterprises 1588 }
-- Product Lines or Generic Product information
-- { bcsi 1 } is reserved
commDev OBJECT IDENTIFIER ::= { bcsi 2 } -- communication devices
-- commDev OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The root OID sub-tree for Communication
-- Devices of Brocade."
-- ::= { bcsi 2 }
fibrechannel OBJECT IDENTIFIER ::= { commDev 1 }
-- fibrechannel OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The root OID sub-tree for Fibre Channel
-- Devices of Brocade."
-- ::= { commDev 1 }
fcSwitch OBJECT IDENTIFIER ::= { fibrechannel 1 }
-- fcSwitch OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The root OID sub-tree for Fibre Channel
-- Switches of Brocade."
-- ::= { fibrechannel 1 }
bcsiReg OBJECT IDENTIFIER ::= { bcsi 3 }
-- bcsiReg OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The root OID sub-tree for Brocade Global Registry."
-- ::= { bcsi 3 }
bcsiModules OBJECT IDENTIFIER ::= { bcsiReg 1 }
-- bcsiModules OBJECT-IDENTITY
-- STATUS current
-- DESCRIPTION "The root OID sub-tree for Brocade Mib Modules."
-- ::= { bcsiReg 1 }
END
-- *******************************************************************
-- Brocade-REG-MIB.my: Brocade Products MIB.
--
-- Feb 2012, Sanjeev C Joshi, Yasar Khan
--
-- Copyright (c) 1996-2002, 2012 by Brocade Communications Systems, Inc.
-- All rights reserved.
--
-- *******************************************************************
Brocade-REG-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-IDENTITY,
enterprises FROM SNMPv2-SMI;
bcsi MODULE-IDENTITY
LAST-UPDATED "201202030000Z"
ORGANIZATION " Brocade Communications Systems, Inc."
CONTACT-INFO
"Brocade Communications Systems, Inc.
Postal: 130 Holger Way
San Jose, CA 95134
U.S.A
Tel: +1-408-333-8000
E-mail: support@Brocade.com
web: www.brocade.com."
DESCRIPTION
"This MIB module defines Structure of Management
Information for the Brocade enterprise and serves as
central repository of all the OIDs under Brocade
enterprise OID tree."
REVISION "201202030000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { enterprises 1588 } -- assigned by IANA
commDev OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for Communication devices of Brocade."
::= { bcsi 2 }
fibrechannel OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for Fibre Channel Devices of Brocade."
::= { commDev 1 }
nos OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for Brocade's NOS products."
::= { commDev 2 }
fcSwitch OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for Fibre Channel Switches of Brocade."
::= { fibrechannel 1 }
bcsiReg OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for Brocade Global Registry."
::= { bcsi 3 }
bcsiModules OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root OID sub-tree for all the Brocade management MIBs."
::= { bcsiReg 1 }
brocadeAgentCapability OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This provides a root object identifier from which
AGENT-CAPABILITIES values may be assigned."
::= { bcsiReg 2 }
END

78
mibs/Brocade-TC-MIB Normal file
View File

@ -0,0 +1,78 @@
--
-- Title: Brocade Registration MIB, Version v5.0
--
-- This is specified based on SMIv2, mainly to ensure that the specification
-- can be parsed easily by off-the-shelf network management product in
-- the market.
--
-- The goal of this mib is to access all the Brocade Enterprise products.
-- This mib file contains the generic textual conventions of Brocade's product.
--
Brocade-TC DEFINITIONS ::= BEGIN
IMPORTS
bcsiModules
FROM Brocade-REG-MIB
TEXTUAL-CONVENTION
FROM SNMPv2-TC
Integer32, MODULE-IDENTITY
FROM SNMPv2-SMI;
bcsiModuleTC MODULE-IDENTITY
LAST-UPDATED "0210030000Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
1745 Technology Drive,
San Jose, CA 95110 U.S.A
Tel: +1-408-392-6061
Fax: +1-408-392-6656
Email: support@Brocade.COM
WEB: www.brocade.com"
DESCRIPTION "The MIB module contains all shared textual conventions
for Brocade specific MIBs.
Copyright (c) 1996-2002 Brocade Communications Systems, Inc.
All rights reserved."
REVISION "0301131430Z" -- Jan 13, 2003 2:30pm
DESCRIPTION "The initial version of this module."
::= { bcsiModules 2 }
-- additional textual conventions
FcWwn ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The World Wide Name (WWN) of Brocade's
specific products and ports."
SYNTAX OCTET STRING (SIZE(8))
SwDomainIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The Fibre Channel domain ID of the switch."
SYNTAX Integer32 (1..239)
SwNbIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Index of the neighbour ISL entry."
SYNTAX Integer32 (1..2048)
SwSensorIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Index of the Sensor entry."
SYNTAX Integer32 (1..1024)
SwPortIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Index of the Port start from 1 upto Maximum
number of ports of the Brocade Switch."
SYNTAX Integer32
SwTrunkMaster ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Index of the Trunk Master start from 1 upto Maximum
number of trunk groups of Brocade Switch."
SYNTAX Integer32
END

2097
mibs/DOT3-OAM-MIB Normal file

File diff suppressed because it is too large Load Diff

127
mibs/FA-EXT-MIB Normal file
View File

@ -0,0 +1,127 @@
--
-- Title: Fibre Channel Switch MIB.
--
FA-EXT-MIB DEFINITIONS ::= BEGIN
IMPORTS
DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC
Integer32, OBJECT-TYPE, OBJECT-IDENTITY,
MODULE-IDENTITY
FROM SNMPv2-SMI
sw
FROM SW-MIB
connUnitPortEntry
FROM FCMGMT-MIB;
faExt MODULE-IDENTITY
LAST-UPDATED "200807291830Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
1745 Technology Drive,
San Jose, CA 95110 U.S.A
Tel: +1-408-392-6061
Fax: +1-408-392-6656
Email: support@Brocade.COM
WEB: www.brocade.com"
DESCRIPTION "The MIB module is Extension for FA-MIB.
Copyright (c) 1996-2003 Brocade Communications Systems, Inc.
All rights reserved."
::= { sw 28 }
swSfpStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwSfpStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This represents the diagnostic stats of SFPs."
::= { faExt 1 }
swSfpStatEntry OBJECT-TYPE
SYNTAX SwSfpStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This represents the diagnostic stats of SFPs"
AUGMENTS {connUnitPortEntry}
::= { swSfpStatTable 1 }
SwSfpStatEntry ::= SEQUENCE {
swSfpTemperature OCTET STRING,
swSfpVoltage OCTET STRING,
swSfpCurrent OCTET STRING,
swSfpRxPower OCTET STRING,
swSfpTxPower OCTET STRING,
swSfpPoweronHrs Integer32,
swSfpOUI OCTET STRING,
swSfpUnitId Integer32
}
swSfpTemperature OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
UNITS "centigrade"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the temperature of SFP"
::= { swSfpStatEntry 1 }
swSfpVoltage OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
UNITS "milli voltage"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the voltage of SFP."
::= { swSfpStatEntry 2 }
swSfpCurrent OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
UNITS "milli amphere"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the current of SFP."
::= { swSfpStatEntry 3 }
swSfpRxPower OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
UNITS "dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the Rx power consumption of SFP."
::= { swSfpStatEntry 4 }
swSfpTxPower OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
UNITS "dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the Tx power consumption of SFP."
::= { swSfpStatEntry 5 }
swSfpPoweronHrs OBJECT-TYPE
SYNTAX Integer32
UNITS "hours"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies the power on hours of SFP.
This is applicable only to 16G SFPs."
::= { swSfpStatEntry 6 }
swSfpOUI OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object represents the OUI of the SFP"
::= { swSfpStatEntry 7 }
swSfpUnitId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object identifies unit ID of SFP.
This is applicable only to QSFP."
::= { swSfpStatEntry 8 }
END

1509
mibs/IBM-BCCUSTOM-MIB Normal file

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,339 @@
-- ***************************************************************************
-- ***************************************************************************
--
-- File : fod.mib
-- Description : MIB definitions for IBM Features On Demand Activation Key
-- functions.
-- By : IBM
-- Version : 1.2
-- Date : March 30, 2011
--
--
-- Copyright (c) 2010-11 IBM All Rights Reserved.
--
--
-- Contains MIB description for:
-- This MIB is to be used to provide configuration support of IBM Features
-- on Demand features.
-- ***************************************************************************
-- ***************************************************************************
-- ***************************************************************************
-- Revisions:
-- ***************************************************************************
IBM-FEATURE-ACTIVATION-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
enterprises, NOTIFICATION-TYPE
FROM SNMPv2-SMI --RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF --RFC2580
DateAndTime, DisplayString
FROM SNMPv2-TC; --RFC2579
ibmFeatureActivationMIB MODULE-IDENTITY
LAST-UPDATED "201103300733Z" --30 March 2011 07:33 GMT
ORGANIZATION "International Business Machines Corp."
CONTACT-INFO
"Fred Bower
International Business Machines Corporation
Systems and Technology Group System x Development
Research Triangle Park, NC, USA
E-mail: bowerf@us.ibm.com"
DESCRIPTION
"This module provides a simple interface for
IBM Features On Demnad Activation Key functions."
-- Revision History
REVISION "201103300733Z" --30 March 2011
DESCRIPTION
"Updated data types and added traps for status
change notification. Clarified return codes
from events."
REVISION "201102021949Z" --2 February 2011
DESCRIPTION
"Added support for SFTP protocol file transfers."
REVISION "201012081833Z" --8 December 2010
DESCRIPTION
"Initial Revision."
::= { ibmArchitecture 31 }
-- IBM enterprise group
ibm OBJECT IDENTIFIER ::= { enterprises 2 }
-- IBM architecture group
ibmArchitecture OBJECT IDENTIFIER ::= { ibm 5 }
-- Features on Demand Objects
ibmFodNotifications OBJECT IDENTIFIER ::= {ibmFeatureActivationMIB 0 }
ibmFodObjects OBJECT IDENTIFIER ::= { ibmFeatureActivationMIB 1 }
ibmFodConformance OBJECT IDENTIFIER ::= { ibmFeatureActivationMIB 2 }
-- ***********************************************************************
-- Activation Key Install/Update
-- ***********************************************************************
-- Feature activation keys can be installed (to activate), uninstalled
-- (to deactivate), exported (for backup purposes), and inventoried.
-- The action desired is set via the ibmFodAction object (which is never
-- read). The required sub-objects and their use is listed here as well
-- as in the DESCRIPTION comments for each of the fields for user
-- understanding.
-- Action: installActivationKey
-- Requires: ibmFodFileUri
-- Process: Installer sets the ibmFodFileUri field to indicate where to
-- retrieve activation key file from, then sets the ibmFodAction to
-- installActivationKey.
-- Result: Activation key is transferred from URI to the target device,
-- validated, and result is available for reading via ibmFodStatus. An
-- alert should also be issued if the key actually changes device state.
-- That is, if the key is successfully validated and stored and function
-- is either queued for activation after a reboot or is activated, an
-- alert should be generated with the updated key status information.
--
-- Action: inventoryInstalledActivationKeys
-- Requires: ibmFodFileUri
-- Process: Administrator sets ibmFodFileUri field to indicate where to
-- place file with results of inventory of device, then sets ibmFodAction
-- to inventoryInstalledActivationKeys.
-- Result: Activation key inventory is transferred to URI from target
-- device and result is available for reading from ibmFodStatus.
-- Inventory file format is comma-separated with fields ordered as
-- follows:
--
-- <Index>,<Status>,<Feature Descriptor Type Description (text)>,
-- <Constraint Descriptor Type Description (text)>:<Constraint Descriptor
-- Type Optional Information (text)> 0..n
--
-- The 0..n notation is to indicate that there may be zero or more
-- constraints for any given activation key. New records start with a
-- newline character after the last constraint. If a constraint does not
-- have optional information text, the colon separator is omitted and a
-- comma denotes the start of the next constraint descriptor type
-- description. This activity should not result in any alerts, as it
-- does not alter activation key state on the device.
--
-- Action: uninstallActivationKey
-- Requires: ibmFodIndex
-- Process: Administrator sets ibmFodIndex with value from inventory
-- report process, above, then sets ibmFodAction to
-- uninstallActivationKey.
-- Result: Activation key is uninstalled and result of action is placed
-- in ibmFodStatus for reading. An alert should also be issued if the
-- action changes device state. That is, if there is a key at the
-- designated index and it is uninstalled, the device key state will
-- change, thus triggering an alert with the updated device information.
--
-- Action: exportActivationKey
-- Requires: ibmFodIndex, ibmFodFileUri
-- Process: Administrator sets ibmFodIndex with value from inventory
-- report process, above, then sets ibmFodFileUri to the desired location
-- for the exported key file to be placed, then sets ibmFodAction to
-- exportActivationKey.
-- Result: Activation key file is exported to designated URI location
-- provided that the index supplied maps to an existing key. Status of
-- the command is placed in ibmFodStatus for reading. No alert will be
-- issued from this activity, as it does not affect activation key state
-- on the device.
--
ibmFodAction OBJECT-TYPE
SYNTAX INTEGER {
installActivationKey(1),
uninstallActivationKey(2),
exportActivationKey(3),
inventoryInstalledActivationKeys(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Target action for activation method.
1 - Install Activation Key
2 - Uninstall Activation Key
3 - Export Activation Key
4 - Inventory Installed Activation Keys"
DEFVAL { 4 }
::= { ibmFodObjects 1 }
ibmFodIndex OBJECT-TYPE
SYNTAX INTEGER (1..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Activation key index to uninstall or export.
This is only required for uninstall and export actions.
This is also used to identify the key associated with alerts."
::= { ibmFodObjects 2 }
ibmFodFileUri OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..1024))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"URI of where key file resides for install and
where it should be placed for export or inventory.
This is not used for uninstall action."
::= { ibmFodObjects 3 }
ibmFodStatus OBJECT-TYPE
SYNTAX INTEGER {
success(1),
rebootRequired(2),
versionMismatch(3),
corruptKeyFile(4),
invalideKeyFileTarget(5),
keyFileNotPresent(6),
communicationFailure(7),
keyStoreFull(8),
ftpServerFull(9),
userAuthenticationFailed(10),
invalidIndex(11),
protocolNotSupported(12),
preRequisiteKeyActionRequired(13),
actionIncompleteDeviceBusy(14),
fileAlreadyExists(15),
permissionProblem(16)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Return status of the last firmware activation method
initiated through SNMP method.
Valid return codes are:
Code Action(s) Meaning
1 1,2,3,4 Success
2 1,2 Reboot Required
3 1 Firmware Version/Update Issue
4 1 Key Corrupt
5 1 Key Not Valid for Device
6 1,2,4 Key File Not Found
7 1,3,4 Failure to Communicate with File Server
8 1 Key Storage Full
9 3,4 TFTP/SFTP Server Storage Full
10 1,3,4 SFTP User/Password Authentication Failed
11 2,3 Invalid Index
12 1,3,4 Protocol Specified in URI Not Supported
13 1,2 Pre-Requisite Key Action Required
14 1,2,3,4 Action Still In Process/Busy
15 3,4 File Already Exists on Server
16 3,4 Permission Problem with Specified URI User"
::= { ibmFodObjects 4 }
ibmFodKeyChangeTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The date and time of the event described in
this notification of activated function status change."
::= { ibmFodObjects 5 }
ibmFodKeyOldStatus OBJECT-TYPE
SYNTAX INTEGER {
noPreviousStatus (1),
keyValid (2),
keyInvalid (3),
keyValidElsewhere (4),
keyFeatureActive (5),
keyFeatureRequiresHostReboot (6),
keyFeatureRequiresBMCReboot (7),
keyExpired (8),
keyUseLimitExceeded (9),
keyInProcessOfValidation (10)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The prior status of the activation key associated
with this status change."
::= { ibmFodObjects 6 }
ibmFodKeyNewStatus OBJECT-TYPE
SYNTAX INTEGER {
keyRemoved (1),
keyValid (2),
keyInvalid (3),
keyValidElsewhere (4),
keyFeatureActive (5),
keyFeatureRequiresHostReboot (6),
keyFeatureRequiresBMCReboot (7),
keyExpired (8),
keyUseLimitExceeded (9),
keyInProcessOfValidation (10),
keyReplaced (11)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The new status of the activation key associated
with this status change."
::= { ibmFodObjects 7 }
ibmFodKeyUpdateData OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"String containing constraint data. This is only used
for ibmFodNewStatus value of keyReplaced (10). Otherwise,
this string should be NULL."
::= { ibmFodObjects 8 }
-- Notifications
ibmFodActivationChangeAlert NOTIFICATION-TYPE
OBJECTS {
ibmFodIndex,
ibmFodKeyChangeTime,
ibmFodKeyOldStatus,
ibmFodKeyNewStatus,
ibmFodKeyUpdateData
}
STATUS current
DESCRIPTION
"This is an SNMP notification of a change to an existing
feature activation on an endpoint. Data in the
notification payload describes the change."
::= { ibmFodNotifications 1 }
-- Conformance Information
-- Compliance Statements
ibmFeatureActivationCompliances OBJECT IDENTIFIER ::= { ibmFodConformance 1 }
ibmFeatureActivationGroups OBJECT IDENTIFIER ::= { ibmFodConformance 2 }
ibmFeatureActivationCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the IBM-FEATURE-ACTIVATION-MIB."
MODULE --This module
MANDATORY-GROUPS { ibmFeatureActivationBaseGroup,
ibmFeatureActivationNotifGroup }
::= { ibmFeatureActivationCompliances 1 }
-- MIB Groupings
ibmFeatureActivationBaseGroup OBJECT-GROUP
OBJECTS {
ibmFodAction,
ibmFodIndex,
ibmFodFileUri,
ibmFodStatus,
ibmFodKeyChangeTime,
ibmFodKeyOldStatus,
ibmFodKeyNewStatus,
ibmFodKeyUpdateData
}
STATUS current
DESCRIPTION
"The group of mandatory objects for all implementations
to be compliant."
::= { ibmFeatureActivationGroups 1 }
ibmFeatureActivationNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { ibmFodActivationChangeAlert }
STATUS current
DESCRIPTION
"The notification group required for compliance in alert
semantics for feature activation implementations."
::= { ibmFeatureActivationGroups 2 }
END

42
mibs/NOS-PRODUCTS-MIB Normal file
View File

@ -0,0 +1,42 @@
NOS-PRODUCTS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
nos
FROM Brocade-REG-MIB;
nosProducts MODULE-IDENTITY
LAST-UPDATED "0110101500Z"
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
120 Holger Way,
San Jose, CA 95134 U.S.A."
DESCRIPTION "A MIB module that represents Brocade
NOS products."
::= { nos 1 }
bcsiRegistration OBJECT IDENTIFIER ::= { nosProducts 1 }
-- OID Registration point for Chassis Types
bcsiChassisTypes OBJECT IDENTIFIER ::= { bcsiRegistration 1 }
-- OID Registration for Card Types
bcsiCardTypes OBJECT IDENTIFIER ::= { bcsiRegistration 2 }
-- Pizzaboxes
vdx6720P24 OBJECT IDENTIFIER ::= { bcsiChassisTypes 1 }
vdx6720P60 OBJECT IDENTIFIER ::= { bcsiChassisTypes 2 }
vdx6730P32 OBJECT IDENTIFIER ::= { bcsiChassisTypes 3 }
vdx6730P76 OBJECT IDENTIFIER ::= { bcsiChassisTypes 4 }
vdx6710P54 OBJECT IDENTIFIER ::= { bcsiChassisTypes 5 }
vdx6746 OBJECT IDENTIFIER ::= { bcsiChassisTypes 112}
END

135
mibs/RESOURCE-MIB Normal file
View File

@ -0,0 +1,135 @@
--
-- Title: Switch CPUorMemory MIB.
--
RESOURCE-MIB DEFINITIONS ::= BEGIN
IMPORTS
DisplayString, TEXTUAL-CONVENTION, TruthValue
FROM SNMPv2-TC
Integer32, OBJECT-TYPE, OBJECT-IDENTITY,
MODULE-IDENTITY
FROM SNMPv2-SMI
sw
FROM SWBASE-MIB;
swCpuOrMemoryUsage MODULE-IDENTITY
LAST-UPDATED "1306051130Z" -- Jun 5, 2013 11:30am
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
130 Holger Way,
San Jose, CA 95134 U.S.A
Tel: +1-408-333-8000
Fax: +1-408-333-8101
Email: support@Brocade.COM
WEB: www.brocade.com"
DESCRIPTION "The MIB module is for system information.
Copyright (c) 1996-2003 Brocade Communications Systems, Inc.
All rights reserved."
REVISION "1104151830Z" -- Apr 15, 2011 6:30pm
DESCRIPTION "Initial version of this module."
REVISION "1306051130Z" -- Jun 5, 2013 11:30am
DESCRIPTION "Updated Syntax for swCpuAction, swMemAction and description for
swCpuUsageLimit, swMemUsageLimit. Also added default values if applicable"
::= { sw 26 }
swCpuUsage OBJECT-TYPE
SYNTAX Integer32(0..100)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "System's cpu usage."
::= { swCpuOrMemoryUsage 1 }
swCpuNoOfRetries OBJECT-TYPE
SYNTAX Integer32 (1..100)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Number of times system should take cpu utilization sample before sending the CPU utilization trap."
DEFVAL { 3 }
::= { swCpuOrMemoryUsage 2 }
swCpuUsageLimit OBJECT-TYPE
SYNTAX Integer32 (1..100)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It describes the CPU usage limit in percentage. If the cpu usage value exceeds the
limit then the appropriate action will be taken based on the swCpuAction value."
DEFVAL { 75 }
::= { swCpuOrMemoryUsage 3 }
swCpuPollingInterval OBJECT-TYPE
SYNTAX Integer32 (10..3600)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Time interval between two memory samples."
DEFVAL { 120 }
::= { swCpuOrMemoryUsage 4 }
swCpuAction OBJECT-TYPE
SYNTAX INTEGER {
none (0),
raslog (1),
snmp (2),
raslogandSnmp (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Specifies the actions to be taken if system
resources exceed the specified threshold."
DEFVAL { none }
::= { swCpuOrMemoryUsage 5 }
swMemUsage OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "System's memory usage."
::= { swCpuOrMemoryUsage 6 }
swMemNoOfRetries OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Number of times system should take memory usage
sample before sending the memory usage trap."
DEFVAL { 3 }
::= { swCpuOrMemoryUsage 7 }
swMemUsageLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "It describes the Memory usage limit in percentage. If the memory usage value
exceeds the limit then the appropriate action will be taken based on the swMemAction value."
DEFVAL { 60 }
::= { swCpuOrMemoryUsage 8 }
swMemPollingInterval OBJECT-TYPE
SYNTAX Integer32 (10..3600)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Time interval between two memory samples."
DEFVAL { 120 }
::= { swCpuOrMemoryUsage 9 }
swMemAction OBJECT-TYPE
SYNTAX INTEGER {
none (0),
raslog (1),
snmp (2),
raslogandSnmp (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Specifies the actions to be taken if system
resources exceed the specified threshold."
DEFVAL { none }
::= { swCpuOrMemoryUsage 10 }
END

50
mibs/SWBASE-MIB Normal file
View File

@ -0,0 +1,50 @@
--
-- Title: Switch Base MIB.
--
-- This is specified based on SMIv2, mainly to ensure that the specification
-- can be parsed easily by off-the-shelf network management product in
-- the market.
--
-- The goal of this mib is to access the switch of
-- Brocade's family
-- NOTE: Load BRCD.mib file before loading this mib file.
--
SWBASE-MIB DEFINITIONS ::= BEGIN
IMPORTS
DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC
Counter32, Integer32, IpAddress,
OBJECT-TYPE, OBJECT-IDENTITY,
MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
fcSwitch, bcsiModules
FROM Brocade-REG-MIB;
swMibModule MODULE-IDENTITY
LAST-UPDATED "1104151830Z" -- Apr 15, 20i11 6:30pm
ORGANIZATION "Brocade Communications Systems, Inc.,"
CONTACT-INFO "Customer Support Group
Brocade Communications Systems,
130 Holger Way,
San Jose, CA 95134 U.S.A
Tel: +1-408-333-8000
Fax: +1-408-333-8101
Email: support@Brocade.COM
WEB: www.brocade.com"
DESCRIPTION "The MIB module is for Brocade's Switch.
Copyright (c) 1996-2003 Brocade Communications Systems, Inc.
All rights reserved."
REVISION "1104151830Z" -- Apr 15, 20i11 6:30pm
DESCRIPTION "The initial version of this module."
::= { bcsiModules 3 }
sw OBJECT-IDENTITY
STATUS current
DESCRIPTION "The OID sub-tree for Brocade's Silkworm Series of Switches."
::= { fcSwitch 1 }
END

1056
mibs/SYSTEM-MIB Normal file

File diff suppressed because it is too large Load Diff