All MIBs › CISCO-EXT-SCSI-MIB › ciscoExtScsiStartLunDisc
ciscoExtScsiStartLunDisc
Module: CISCO-EXT-SCSI-MIB
OID (symbolic): CISCO-EXT-SCSI-MIB::ciscoExtScsiStartLunDisc
OID (numeric): 1.3.6.1.4.1.9.9.299.1.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: If this object is set to 'startLocalDiscovery', then only the directly attached SCSI target devices/ports and/or LUNs associated with them on all VSANs will be discovered.
If this object is set to 'startRemoteDiscovery', then all SCSI target devices/ports and/or LUNs associated with them on all VSANs in the whole fabric, except the directly attached ones, will be discovered.
If this object is set to 'startDiscovery', then both the above discoveries will be carried out.
If this object is set to 'startPartialDiscovery', then all SCSI target devices/ports and/or LUNs associated with them on the domain IDs and VSANs specified in the ciscoExtScsiPartialLunDiscTable, will be discovered. If the ciscoExtScsiPartialLunDiscTable is empty, then no SCSI target devices/ports will be discovered.
If this object is set to 'startPortBasedDiscovery', then all LUNs/targets associated with the port specified by ciscoExtScsiLunDiscPortId object will be discovered. If the ciscoExtScsiLunDiscPortId object is not set to a valid value, then no LUNs/targets will be discovered. The value of ciscoExtScsiLunDiscVsanId object should be set to the value of the VSAN on which the port based discovery is to be carried out.
No action is taken if this object is set to 'noop'.
The value of this object when read is always 'noop'.
After a discovery has been triggered, this object cannot be set again to trigger another discovery, when the value of ciscoExtScsiLunDiscStatus is 'inProgress'.
In all the above cases, if the ciscoExtScsiLunDiscOs object is set to a particular Operating System, then the discovery of the LUNs will take place only for that Operating System.
What is ciscoExtScsiStartLunDisc?
A read-write control that triggers SCSI target/LUN discovery on the switch, letting an operator choose between discovering only directly attached (local) devices on all VSANs or initiating remote discovery.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.299.1.1.3 snmpwalk -v2c -c public <target> CISCO-EXT-SCSI-MIB::ciscoExtScsiStartLunDisc
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.299.1.1.3.1 snmpget -v2c -c public <target> CISCO-EXT-SCSI-MIB::ciscoExtScsiStartLunDisc.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.299.1.1.3.1 i <value>
Start monitoring Cisco MDS Fibre Channel SAN switch/director with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-EXT-SCSI-MIB::ciscoExtScsiStartLunDisc OID value, configure state conditions and alerts, and monitor any Cisco MDS Fibre Channel SAN switch/director from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.299 | ciscoExtScsiMIB | CISCO-EXT-SCSI-MIB |
| 1.3.6.1.4.1.9.9.299.1 | ciscoExtScsiMIBObjects | CISCO-EXT-SCSI-MIB |
| 1.3.6.1.4.1.9.9.299.1.1 | ciscoExtScsiConfiguration | CISCO-EXT-SCSI-MIB |
| 1.3.6.1.4.1.9.9.299.1.1.3 | ciscoExtScsiStartLunDisc | CISCO-EXT-SCSI-MIB |