All MIBs › FJDARY-E101 › fjdaryPfcachesluInfo
fjdaryPfcachesluInfo
Module: FJDARY-E101
OID (symbolic): FJDARY-E101::fjdaryPfcachesluInfo
OID (numeric): 1.3.6.1.4.1.211.1.21.1.101.5.12.2.1.2
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-only
Description: The value of this object indicates the SLU performance data gathered
in cache layer.
byte 0 byte 1 byte 2 byte 3
+------------+------------+------------+------------+
0x00| CACHE SLU#index*4 Info (48 bytes) |
+------------+------------+------------+------------+
0x30| CACHE SLU#index*4+1 Info (48 bytes) |
+------------+------------+------------+------------+
0x60| CACHE SLU#index*4+2 Info (48 bytes) |
+------------+------------+------------+------------+
0x90| CACHE SLU#index*4+3 Info (48 bytes) |
+------------+------------+------------+------------+
CACHE SLU information:
byte 0 byte 1 byte 2 byte 3
+------------+------------+------------+------------+
0x00| Read Command Count |
+------------+------------+------------+------------+
0x04| Write Command Count |
+------------+------------+------------+------------+
0x08| Read Hit Count |
+------------+------------+------------+------------+
0x0c| Write Hit Count |
+------------+------------+------------+------------+
0x10| Pre-fetch Read Hit Count |
+------------+------------+------------+------------+
0x14| Read Block Count |
+------------+------------+------------+------------+
0x18| Write Block Count |
+------------+------------+------------+------------+
0x1c| Staging Count |
+------------+------------+------------+------------+
0x20| Writeback Count |
+------------+------------+------------+------------+
0x24| Read Miss Staging Count |
+------------+------------+------------+------------+
0x28| Sequential Read Count |
+------------+------------+------------+------------+
0x2c| Sequential Write Count |
+------------+------------+------------+------------+What is fjdaryPfcachesluInfo?
Packs the same category of cache-layer statistics as fjdaryPfcacheoluInfo (read/write command and hit counts, staging, writeback, sequential-access counts) but measured at the finer-grained SLU (segment) level rather than the whole OLU. Admins use this when a volume-level (OLU) cache metric looks poor and they need to isolate which underlying segment is responsible.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.211.1.21.1.101.5.12.2.1.2 snmpwalk -v2c -c public <target> FJDARY-E101::fjdaryPfcachesluInfo
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.211.1.21.1.101.5.12.2.1.2.1 snmpget -v2c -c public <target> FJDARY-E101::fjdaryPfcachesluInfo.1
Start monitoring Fujitsu ETERNUS DX100 S1 / E101-series disk array with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FJDARY-E101::fjdaryPfcachesluInfo OID value, configure state conditions and alerts, and monitor any Fujitsu ETERNUS DX100 S1 / E101-series disk array from a single console.
OID Breakdown
Upper-level ancestors (10 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.211 | fujitsu | Alert-Definition-Originator-MIB |
| 1.3.6.1.4.1.211.1 | product | CFAB-MIB |
| 1.3.6.1.4.1.211.1.21 | storage | ETERNUS-OR30-SV-MIB |
| 1.3.6.1.4.1.211.1.21.1 | nsp | ETERNUS-OR30-SV-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.211.1.21.1.101 | fjdarye101 | FJDARY-E101 |
| 1.3.6.1.4.1.211.1.21.1.101.5 | fjdaryPerformance | FJDARY-E101 |
| 1.3.6.1.4.1.211.1.21.1.101.5.12 | fjdaryPfcacheslu | FJDARY-E101 |
| 1.3.6.1.4.1.211.1.21.1.101.5.12.2 | fjdaryPfcachesluTable | FJDARY-E101 |
| 1.3.6.1.4.1.211.1.21.1.101.5.12.2.1 | fjdaryPfcachesluEntry | FJDARY-E101 |
| 1.3.6.1.4.1.211.1.21.1.101.5.12.2.1.2 | fjdaryPfcachesluInfo | FJDARY-E101 |