MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 10 (ciscoExperiment). 69 (ciscoMetroPhyMIB). 1 (ciscoMetroPhyMIBObjects). 1 (cmPhyIf). 1 (cmPhyIfTable). 1 (cmPhyIfEntry). 9 (cmPhyIfTxBufferSize)
OID : 1.3.6.1.4.1.9.10.69.1.1.1.1.9
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoExperiment. ciscoMetroPhyMIB. ciscoMetroPhyMIBObjects. cmPhyIf. cmPhyIfTable. cmPhyIfEntry. cmPhyIfTxBufferSize
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.9.10.69.1.1.1.1.9
Module CISCO-METRO-PHY-MIB (CISCO)
NomcmPhyIfTxBufferSize
Accesreadwrite
Statuscurrent
DescriptionThis object applies when circuit emulation of the client protocol is used. It allows the management client to configure the size of the transmit buffer on the client port. A value of 0 implies that this object does not apply to this interface. Controlling the size of the transmit buffer on a client port may be essential in scenarios where packet streams from various client ports are aggregated onto a single trunk port. The latency associated with an elementary stream received on a client port, from the trunk port is influenced by the nature of other elementary streams in the aggregate. For example, a giant packet in one stream will increase latency in processing packets in other elementary streams. The size of the transmit buffer on the client port must be configured proportional to this expected latency. Increasing the buffer size when latency is higher helps in reassembly of fragmented packets before transmitting them to the client device. Note that increasing the buffer size results in higher latency even when the elementary packet stream is not subject to high jitters. Refer to the platform specific documentation for guidelines on configuring this buffer size.
Unitebytes
SyntaxeUnsigned32 (0...65536)