Appendix E Glossary - Network Critical SmartNA-X User Manual

G
LOSSARY
E –
community string
A text string used to authenticate messages between a management station and an SNMP v1/v2c engine.
context
Context name, or "context" in short, is a collection of management information accessible by an SNMP entity.
An item of management information may exist in more than one context. An SNMP entity potentially has
access to many contexts. In other words, if a management information has been defined under certain context
by an SNMPv3 entity, then any management application can access that information by giving that context
name. The "context name" is an octet string which has at least one management information.
engine-id
An engine ID is defined as the administratively unique identifier of an SNMPv3 engine, and is used for
identification. An engine-id is also used to compute the security digest for authentication and encryption. Please
refer to RFC 3411, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management
Frameworks" for more details.
Failsafe/fail-over
Failsafe (or fail-over) maintains full-duplex pass through capability to protect network links from downtime in
the event of a product failure.
Link failure propagation (LFP)
LFP allows attached network devices to detect if link state is lost on the adjacent network device. In effect, LFP
simulates direct connection of the two devices by a cable, in that if one of the connected devices fails the other
device will immediately be taken down.
Management information base (MIB)
SNMP itself does not define which information (which variables) a managed system should offer. Rather,
SNMP uses an extensible design, where the available information is defined by management information bases
(MIBs). MIBs describe the structure of the management data of a device subsystem; they use a hierarchical
namespace containing object identifiers (OID). Each OID identifies a variable that can be read or set via
SNMP. MIBs use the notation defined by ASN.1.
RADIUS
RADIUS (Remote Authentication Dial-In User Service) enables you to use up to three servers (one primary server
and one or two backups) and maintain separate authentication and accounting for each RADIUS server
employed. For authentication, this allows a different password for each user instead of having to rely on
DRAFT
A
PPENDIX
E
219