All MIBs › HH3C-L4RDT-MIB › hh3cL4RedirectCacheRedirectionStatus
hh3cL4RedirectCacheRedirectionStatus
Module: HH3C-L4RDT-MIB
OID (symbolic): HH3C-L4RDT-MIB::hh3cL4RedirectCacheRedirectionStatus
OID (numeric): 1.3.6.1.4.1.25506.2.10.1.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This object returns the current state of traffic redirection to the cache.
If redirection is disabled, this object shall return disabledNotRedirecting(1).
If a unit cannot be selected to perform the cache health check, this object shall return enabledNoHealthChecker(2).
If the software is determining if the cache is able to do redirection(this will happen when the redirection state transitions from disabled to enabled), this object shall return enabledHealthChecking(3).
If the cache health check succeeded but the hardware is unable to support redirection to the cache port, this object shall return enabledHealthCheckOKNotRedirecting(4).
If the latest health check of the cache has failed, this object shall return enabledHealthCheckFailed(5).
If the cache is in use and traffic is being redirected to it, this object shall return enabledRedirecting(6).
The default value is disabledNotRedirecting(1).
What is hh3cL4RedirectCacheRedirectionStatus?
This read-only object reports the current redirection state of Layer 4 traffic to a specific Web Cache device identified by its IP address in the hh3cL4RedirectCacheTable, returning one of six values from disabledNotRedirecting(1) to enabledRedirecting(6). An admin polls this value to determine why traffic isn't reaching a configured cache, for example distinguishing a cache that's still running its health check (enabledHealthChecking) from one whose latest check failed (enabledHealthCheckFailed) or one that's actively redirecting. For instance, if a newly enabled cache entry shows enabledHealthCheckFailed(5) instead of enabledRedirecting(6), the admin knows the health checker could not validate the cache device and traffic is still bypassing it.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.10.1.1.2 snmpwalk -v2c -c public <target> HH3C-L4RDT-MIB::hh3cL4RedirectCacheRedirectionStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.10.1.1.2.1 snmpget -v2c -c public <target> HH3C-L4RDT-MIB::hh3cL4RedirectCacheRedirectionStatus.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> hh3cL4RedirectCacheRedirectionStatus.1
Start monitoring H3C switches/routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-L4RDT-MIB::hh3cL4RedirectCacheRedirectionStatus OID value, configure state conditions and alerts, and monitor any H3C switches/routers 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.25506 | hh3c | HH3C-OID-MIB |
| 1.3.6.1.4.1.25506.2 | hh3cCommon | HH3C-OID-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.25506.2.10 | hh3cL4Redirect | HH3C-L4RDT-MIB |
| 1.3.6.1.4.1.25506.2.10.1 | hh3cL4RedirectCacheTable | HH3C-L4RDT-MIB |
| 1.3.6.1.4.1.25506.2.10.1.1 | hh3cL4RedirectCacheEntry | HH3C-L4RDT-MIB |
| 1.3.6.1.4.1.25506.2.10.1.1.2 | hh3cL4RedirectCacheRedirectionStatus | HH3C-L4RDT-MIB |