MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 38 (ciscoLecsMIB). 1 (ciscoLecsMIBObjects). 2 (config). 5 (lecsLesConfigTable). 1 (lecsLesConfigEntry). 2 (lecsLesPriority)
OID : 1.3.6.1.4.1.9.9.38.1.2.5.1.2
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoLecsMIB. ciscoLecsMIBObjects. config. lecsLesConfigTable. lecsLesConfigEntry. lecsLesPriority
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.9.9.38.1.2.5.1.2
Module CISCO-LECS-MIB (CISCO)
NomlecsLesPriority
Accesreadwrite
Statuscurrent
Description The relative priority of the LES. The lower this number the more priority is given the LES for servicing the ELAN. Such that a higher priority LES will supersede operation of the ELAN in the presence of a lower priority LES. Note that the LECS will adjust the number entered to fit into a contiguous numbering space equalling the number of LESs defined for the particular ELAN. For example if there is one LES defined for an ELAN then that LES's priority will always be zero since there are no other LESs to contend with. Setting that LESs priority to ten (e.g.) will work but the net result will be that the priority will still be zero (as will be verified by consequent retrieval of this objects value). If a second LES is defined for this ELAN with a priority of ten (e.g.) the net result would be that the second LES will have a priority of one since it is the only other LES for that ELAN and behind in priority from the first LES. If the second LES were given a priority of zero at any time then it would keep the priority of zero and the first LES would transition to having a priority of one. Note that defining a new LES with a priority already in existance by another LES has the effect of giving the new LES the designated priority and reducing the priority (numerically increasing) of all LESs equal to and below it in rank. Likewise, deleting a LES from this table will cause LESs below it in priority (numerically greater) to move up in the table (modifying their priority value to be one less) to fill in the now empty slot. In this way a table, with at least one entry, should always contain entries with priorities including zero up to the number of entries minus one (0..(n-1)).
SyntaxeInteger32 (0...10000)