Hi There
I despair somewhat at. Please Help!
I have found all required OID's for the switches and OS64xx OS68xx.
But now I can not find the OID's for the OS6900 Switche, for the following queries:
"Operational Status, Power Supply, FAN's, Serial, Model, Software Rev, CPU (%), Memory (%), Temperatur"
I have this walk outputs to identify the devices in the Switch, but do not find the OID to ask this device ID's about there status:
Device List OS6900
29.06.2016 14:59:51 (16 ms) : Walk 1.3.6.1.2.1.47.1.1.1.1.7
29.06.2016 14:59:51 (22 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.1 = "NI" [ASN_OCTET_STR]
29.06.2016 14:59:51 (28 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.2 = "NI" [ASN_OCTET_STR]
29.06.2016 14:59:51 (33 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.65 = "" [ASN_OCTET_STR]
29.06.2016 14:59:51 (39 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.209 = "Chassis" [ASN_OCTET_STR]
29.06.2016 14:59:51 (44 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.275 = "PS-1" [ASN_OCTET_STR]
29.06.2016 14:59:51 (50 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.276 = "PS-2" [ASN_OCTET_STR]
29.06.2016 14:59:51 (56 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.451 = "FAN-TRAY" [ASN_OCTET_STR]
----------------------------------------------------
If someone is interesstet here are the OID's that worked for the OS64xx OS68xx:
Device List OS68xx (also works for OS64xx)
28.06.2016 16:13:19 (19 ms) : Walk 1.3.6.1.2.1.47.1.1.1.1.7
28.06.2016 16:13:19 (40 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.1 = "NI-1" [ASN_OCTET_STR]
28.06.2016 16:13:19 (49 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.2 = "NI-2" [ASN_OCTET_STR]
28.06.2016 16:13:19 (58 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.65 = "CMM-A" [ASN_OCTET_STR]
28.06.2016 16:13:19 (68 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.66 = "CMM-B" [ASN_OCTET_STR]
28.06.2016 16:13:19 (81 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.97 = "PS-1" [ASN_OCTET_STR]
28.06.2016 16:13:19 (90 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.98 = "PS-2" [ASN_OCTET_STR]
28.06.2016 16:13:19 (99 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.100 = "PS-1" [ASN_OCTET_STR]
28.06.2016 16:13:19 (109 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.101 = "PS-2" [ASN_OCTET_STR]
28.06.2016 16:13:19 (119 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.132 = "port" [ASN_OCTET_STR]
28.06.2016 16:13:20 (140 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.156 = "port" [ASN_OCTET_STR]
28.06.2016 16:13:20 (151 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.157 = "port" [ASN_OCTET_STR]
28.06.2016 16:13:20 (161 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.569 = "Virtual Chassis" [ASN_OCTET_STR]
28.06.2016 16:13:20 (170 ms) : 1.3.6.1.2.1.47.1.1.1.1.7.570 = "Virtual Chassis" [ASN_OCTET_STR]
Operational Status:
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.1 Stack 1
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.2 Stack 2
Power Supply:
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.97 Power Supply 1 Chassis 1
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.98 Power Supply 2 Chassis 1
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.100 Power Supply 1 Chassis 2
1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.101 Power Supply 1 Chassis 2
FAN:
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.1 FAN 1 Chassis 1
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.2 FAN 2 Chassis 1
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.3 FAN 3 Chassis 1
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.570.1 FAN 1 Chassis 2
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.570.2 FAN 2 Chassis 2
1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.570.3 FAN 3 Chassis 2
Serial:
1.3.6.1.2.1.47.1.1.1.1.11.1 Stack 1
1.3.6.1.2.1.47.1.1.1.1.11.2 Stack 2
Model:
1.3.6.1.2.1.47.1.1.1.1.13.1 Stack 1
1.3.6.1.2.1.47.1.1.1.1.13.2 Stack 2
Software Rev:
1.3.6.1.2.1.47.1.1.1.1.10.1 Stack 1
1.3.6.1.2.1.47.1.1.1.1.10.2 Stack 2
CPU:
1.3.6.1.4.1.6486.800.1.2.1.16.1.1.1.13.0
Memory:
1.3.6.1.4.1.6486.800.1.2.1.16.1.1.1.9.0
Temperatur:
1.3.6.1.4.1.6486.800.1.2.1.16.1.1.1.17.0
POE:
1.3.6.1.4.1.6486.800.1.2.1.27.1.1.2.1.1.1
Seeking the SNMP OID's for...
-
- Member
- Posts: 2
- Joined: 04 Jul 2016 09:07
Seeking the SNMP OID's for...
Andreas Freitag
-
- Member
- Posts: 2
- Joined: 04 Jul 2016 09:07
Re: Seeking the SNMP OID's for...
Update: I have found the OID's with a lot of trying... hard work ... hope they realy work, I am somewhat unsure about the FAN Tray?!
And i still search the OID to get the firmware/software version
-----------------------------------------------------
Operational Status:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.209 Stack 1
Power Supply:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.275 Power Supply 1 Chassis 1
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.276 Power Supply 2 Chassis 1
FAN:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.451 FAN-TRAY
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.1 FAN 1
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.2 FAN 2
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.3 FAN 3
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.4 FAN 4
Serial:
1.3.6.1.2.1.47.1.1.1.1.11.209 Stack 1 Text
Model:
1.3.6.1.2.1.47.1.1.1.1.13.209 Stack 1 Text
Does not work! Software Rev:
1.3.6.1.2.1.47.1.1.1.1.10.209 Stack 1 Text
CPU:
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.11.0 %
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.11.1 %
Memory:
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.8.0 %
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.8.1 %
Temperatur:
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.8.209 °C
And i still search the OID to get the firmware/software version
-----------------------------------------------------
Operational Status:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.209 Stack 1
Power Supply:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.275 Power Supply 1 Chassis 1
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.276 Power Supply 2 Chassis 1
FAN:
1.3.6.1.4.1.6486.801.1.1.1.1.1.1.1.1.451 FAN-TRAY
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.1 FAN 1
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.2 FAN 2
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.3 FAN 3
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.11.1.2.209.4 FAN 4
Serial:
1.3.6.1.2.1.47.1.1.1.1.11.209 Stack 1 Text
Model:
1.3.6.1.2.1.47.1.1.1.1.13.209 Stack 1 Text
Does not work! Software Rev:
1.3.6.1.2.1.47.1.1.1.1.10.209 Stack 1 Text
CPU:
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.11.0 %
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.11.1 %
Memory:
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.8.0 %
1.3.6.1.4.1.6486.801.1.2.1.16.1.1.1.1.1.8.1 %
Temperatur:
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.8.209 °C
Andreas Freitag
Re: Seeking the SNMP OID's for...
hello
for 6900 sw version
/usr/bin/snmpwalk 1.1.1.1 -t 3 -v 3 -u myusername -l authPriv -a SHA -A mypassword -x DES -X mypassword -O Q .1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = Alcatel-Lucent OS6900-X20 7.3.4.270.R02 Service Release, May 31, 2016.
or
.1.3.6.1.2.1.1.1.0 = STRING: Alcatel-Lucent OS6900-X20 7.3.4.270.R02 Service Release, May 31, 2016.
Cedric
for 6900 sw version
/usr/bin/snmpwalk 1.1.1.1 -t 3 -v 3 -u myusername -l authPriv -a SHA -A mypassword -x DES -X mypassword -O Q .1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = Alcatel-Lucent OS6900-X20 7.3.4.270.R02 Service Release, May 31, 2016.
or
.1.3.6.1.2.1.1.1.0 = STRING: Alcatel-Lucent OS6900-X20 7.3.4.270.R02 Service Release, May 31, 2016.
Cedric
Re: Seeking the SNMP OID's for...
Here good output where you look into mib file, good way to find info instead of looking at oid.
/usr/bin/snmpwalk 11.1.11.1 -t 3 -v 3 -u myuser -l authPriv -a SHA -A mypassword -x DES -X mypassword -O q -m +ALCATEL7-IND1-LAG-MIB (this is on same line as snmpwalk ) alclnkaggAggNbrAttachedPorts (end of snmp querie)
answer :
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000010 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000011 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000012 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000013 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000014 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000015 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000016 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000017 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000018 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000019 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000051 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000053 2
Here you can see Lag id 10 to 53 contain 2 member up
If you have one port down in lag you will have 1
I use this querie to be sure I have always my 2 ports up in my laggs.
So here my mib file
root@nagiosng:/usr/local/nagios/libexec# locate ALCATEL-IND1-LAG-MIB
/usr/share/snmp/mibs/ALCATEL-IND1-LAG-MIB.mib
You see I rename from ALCATEL-IND1-LAG-MIB to ALCATEL7-IND1-LAG-MIB the definition part inside the file
-> this because I have mib file for 9000 chassis and it is the same name for R6 and R7 but not pointing to same OID. So manually I change it to querie good
file.
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-LAG-MIB.mib
ALCATEL7-IND1-LAG-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, Counter32, Integer32, TimeTicks
FROM SNMPv2-SMI
MacAddress, TEXTUAL-CONVENTION, RowStatus
FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB
PortList
FROM Q-BRIDGE-MIB
LacpKey,LacpState,ChurnState
FROM IEEE8023-LAG-MIB
softentIND1LnkAgg
FROM ALCATEL7-IND1-BASE; -> I rename this dependie to because same name as R6
Lets go to file ALCATEL-IND1-BASE and rename definition to ALCATEL7-IND1-BASE so all dependencies will work ....
root@nagiosng:/usr/local/nagios/libexec# locate ALCATEL-IND1-BASE
/usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
ALCATEL7-IND1-BASE DEFINITIONS ::= BEGIN -> here I rename definition
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
FROM
SNMPv2-SMI;
alcatelIND1BaseMIB MODULE-IDENTITY
LAST-UPDATED "201005130000Z"
ORGANIZATION "Alcatel-Lucent"
CONTACT-INFO
"Please consult with Customer Service to ensure the most appropriate
version of this document is used with the products in question:
Alcatel-Lucent, Enterprise Solutions Division
(Formerly Alcatel Internetworking, Incorporated)
26801 West Agoura Road
Agoura Hills, CA 91301-5122
United States Of America
All dependencies files must be in /usr/share/snmp/mibs/
Take note that file-name must not be equal definition name
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
ALCATEL7-IND1-BASE DEFINITIONS ::= BEGIN
Take some time to troubleshoot and find issue with same definition name between R6 and R7 so i think it will help you.
Dive in text mib file and you will find you "bonheur".
Cedric
/usr/bin/snmpwalk 11.1.11.1 -t 3 -v 3 -u myuser -l authPriv -a SHA -A mypassword -x DES -X mypassword -O q -m +ALCATEL7-IND1-LAG-MIB (this is on same line as snmpwalk ) alclnkaggAggNbrAttachedPorts (end of snmp querie)
answer :
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000010 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000011 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000012 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000013 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000014 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000015 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000016 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000017 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000018 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000019 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000051 2
ALCATEL7-IND1-LAG-MIB::alclnkaggAggNbrAttachedPorts.40000053 2
Here you can see Lag id 10 to 53 contain 2 member up
If you have one port down in lag you will have 1
I use this querie to be sure I have always my 2 ports up in my laggs.
So here my mib file
root@nagiosng:/usr/local/nagios/libexec# locate ALCATEL-IND1-LAG-MIB
/usr/share/snmp/mibs/ALCATEL-IND1-LAG-MIB.mib
You see I rename from ALCATEL-IND1-LAG-MIB to ALCATEL7-IND1-LAG-MIB the definition part inside the file
-> this because I have mib file for 9000 chassis and it is the same name for R6 and R7 but not pointing to same OID. So manually I change it to querie good
file.
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-LAG-MIB.mib
ALCATEL7-IND1-LAG-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, Counter32, Integer32, TimeTicks
FROM SNMPv2-SMI
MacAddress, TEXTUAL-CONVENTION, RowStatus
FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB
PortList
FROM Q-BRIDGE-MIB
LacpKey,LacpState,ChurnState
FROM IEEE8023-LAG-MIB
softentIND1LnkAgg
FROM ALCATEL7-IND1-BASE; -> I rename this dependie to because same name as R6
Lets go to file ALCATEL-IND1-BASE and rename definition to ALCATEL7-IND1-BASE so all dependencies will work ....
root@nagiosng:/usr/local/nagios/libexec# locate ALCATEL-IND1-BASE
/usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
ALCATEL7-IND1-BASE DEFINITIONS ::= BEGIN -> here I rename definition
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
FROM
SNMPv2-SMI;
alcatelIND1BaseMIB MODULE-IDENTITY
LAST-UPDATED "201005130000Z"
ORGANIZATION "Alcatel-Lucent"
CONTACT-INFO
"Please consult with Customer Service to ensure the most appropriate
version of this document is used with the products in question:
Alcatel-Lucent, Enterprise Solutions Division
(Formerly Alcatel Internetworking, Incorporated)
26801 West Agoura Road
Agoura Hills, CA 91301-5122
United States Of America
All dependencies files must be in /usr/share/snmp/mibs/
Take note that file-name must not be equal definition name
root@nagiosng:/usr/local/nagios/libexec# more /usr/share/snmp/mibs/ALCATEL-IND1-BASE.mib
ALCATEL7-IND1-BASE DEFINITIONS ::= BEGIN
Take some time to troubleshoot and find issue with same definition name between R6 and R7 so i think it will help you.
Dive in text mib file and you will find you "bonheur".
Cedric
Re: Seeking the SNMP OID's for...
Hi
I’ve been trying to find info on an ALU OID – maybe someone can help. It’s from the 6900 core switch:
1.3.6.1.4.1.6486.801.1.2.1.23.1.0.1
thanks
cesar
I’ve been trying to find info on an ALU OID – maybe someone can help. It’s from the 6900 core switch:
1.3.6.1.4.1.6486.801.1.2.1.23.1.0.1
thanks
cesar
- David_Klancar
- Member
- Posts: 12
- Joined: 01 Dec 2017 04:56
Re: Seeking the SNMP OID's for...
Hi Cesar,
this oid refers to a TRAP named alaDSTrap:
alaDoSTrap 1.3.6.1.4.1.6486.801.1.2.1.23.1.0.1
-> The DoS trap indicates that the sending agent has received DoS attack
Best regards
David
this oid refers to a TRAP named alaDSTrap:
alaDoSTrap 1.3.6.1.4.1.6486.801.1.2.1.23.1.0.1
-> The DoS trap indicates that the sending agent has received DoS attack
Best regards
David