MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 6486 (alcatel). 801 (alcatelIND1BaseMIB). 1 (alcatelIND1Management). 1 (managementIND1Hardware). 1 (hardwareIND1Entities). 2 (hardentIND1System). 1 (alcatelIND1SystemMIB). 1 (alcatelIND1SystemMIBObjects). 6 (systemSwitchLogging). 15 (systemSwitchLoggingSysLogFacilityId)
OID : 1.3.6.1.4.1.6486.801.1.1.1.2.1.1.6.15
TXT : iso. org. dod. internet. private. enterprises. alcatel. alcatelIND1BaseMIB. alcatelIND1Management. managementIND1Hardware. hardwareIND1Entities. hardentIND1System. alcatelIND1SystemMIB. alcatelIND1SystemMIBObjects. systemSwitchLogging. systemSwitchLoggingSysLogFacilityId
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.6486.801.1.1.1.2.1.1.6.15
Module ALCATEL-IND1-SYSTEM-MIB (Alcatel)
NomsystemSwitchLoggingSysLogFacilityId
Accesreadwrite
Statuscurrent
DescriptionThis textual convention enumerates the facilities that originate syslog messages. The Facilities of syslog messages are numerically coded with decimal values. Some of the operating system daemons and processes are traditionally designated by the Facility values given below. Daemons and processes that do not have an explicitly assigned Facility may use any of the 'local use' Facilities or they may use the 'user-level' Facility. For interoperability and backwards compatibility reasons, mapping specified in this document between a label which represents a Facility and the value which represents the corresponding code, is normative. So the mapping from a label configured by operators in syslog.conf or equivalent will consistently map to the same Facility code regardless of implementation, but the label itself is often semantically meaningless, because it is impractical to attempt to enumerate all possible facilities, and the enumeration (label and corresponding value) that is used by an actual Facility is, and has historically been, implementation-dependent. For example, the foobar application might log messages as having come from local7, even though there is no 'local' process on the device, and the operator can configure syslog.conf to have local7.critical messages be relayed, even though there might be multiple facilities using Facility local7. This is typical current practice, and originators, relays and collectors know how to handle this situation. For improved accuracy, the foobar application can also include an APPNAME Structured Data Element.
SyntaxeSysLogFacilityId (ALCATEL-IND1-SYSTEM-MIB)