etsysSyslogServerDefaultUdpPort

ENTERASYS-SYSLOG-CLIENT-MIB · .1.3.6.1.4.1.5624.1.2.14.2.5
Commands MIB view Table view

Object

scalar r/w SyslogUdpPort 
The default UDP port number that the managed entity is
using to send syslog messages.
          
This value will be used as the default value for
etsysSyslogServerUdpPort when creating rows in the
etsysSyslogServerTable and either:
          
1.)  no value is specified for etsysSyslogServerUdpPort, or
          
2.)  etsysSyslogServerUdpPort is implemented read-only.
          
If etsysSyslogServerUdpPort is implemented read-only,
and this value is changed, it should affect the UDP
port that is used to send syslog messages to all
servers as soon as it is practical.
          
This parameter value is maintained across system reboots.

Context

MIB
ENTERASYS-SYSLOG-CLIENT-MIB
OID
.1.3.6.1.4.1.5624.1.2.14.2.5
Type
scalar
Access
readwrite
Status
current
Parent
etsysSyslogServer
Groups
1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogServerDefaultUdpPort.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogServerDefaultUdpPort'

Syntax

SyslogUdpPort
Source
SyslogUdpPort
Base type
Unsigned32

Values & Constraints

Type Constraints
range: 0..65535

Conformance

Member of
etsysSyslogServerDefaultsGroup
Compliance refinements
etsysSyslogClientCompliance readonly
Write access is not required for implementations that
do not support configuring the UDP port number at all,
or do not want to support a configurable default.
Hopefully, it is only the later.
etsysSyslogClientCompliance2 readonly
Write access is not required for implementations that
do not support configuring the UDP port number at all,
or do not want to support a configurable default.
Hopefully, it is only the later.
etsysSyslogClientCompliance3 readonly
Write access is not required for implementations that
do not support configuring the UDP port number at all,
or do not want to support a configurable default.
Hopefully, it is only the later.