TN-SERV-MIB :: tnSvcTlsStpBridgeMaxHops

MIB Reference — IPNetwork Monitor

All MIBsTN-SERV-MIBtnSvcTlsStpBridgeMaxHops

tnSvcTlsStpBridgeMaxHops

Module: TN-SERV-MIB

OID (symbolic): TN-SERV-MIB::tnSvcTlsStpBridgeMaxHops

OID (numeric): 1.3.6.1.4.1.7483.6.1.2.4.2.3.1.53

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description:

The value of the object tnSvcTlsStpBridgeMaxHops specifies the maximum number of hops (known as 'MaxHops' in 802.1Q).

What is tnSvcTlsStpBridgeMaxHops?

This OID sets the maximum number of bridge hops allowed before spanning tree stops forwarding frames. Operators configure this to prevent infinite loops in large networks. For example, setting max hops to 20 ensures that if a loop exists with more than 20 hops, spanning tree will eventually block it.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.4.2.3.1.53
snmpwalk -v2c -c public <target> TN-SERV-MIB::tnSvcTlsStpBridgeMaxHops

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.4.2.3.1.53.1
snmpget -v2c -c public <target> TN-SERV-MIB::tnSvcTlsStpBridgeMaxHops.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.7483.6.1.2.4.2.3.1.53.1 i <value>

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.7483tropicTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6tnProductsTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6.1tnSRMIBTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6.1.2tnSRObjsTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6.1.2.4tnServObjsTN-SERV-MIB
1.3.6.1.4.1.7483.6.1.2.4.2tnSvcObjsTN-SERV-MIB
1.3.6.1.4.1.7483.6.1.2.4.2.3tnSvcTlsInfoTableTN-SERV-MIB
1.3.6.1.4.1.7483.6.1.2.4.2.3.1tnSvcTlsInfoEntryTN-SERV-MIB
1.3.6.1.4.1.7483.6.1.2.4.2.3.1.53tnSvcTlsStpBridgeMaxHopsTN-SERV-MIB