Comtech EF Data KPA - Manual (Page 64)

KPA Ku-Band Indoor Solid-State Power Amplifier Revision 1
Ethernet Management MN/KPA.IOM
6–2
6.3.1 Management Information Base (MIB) Files
MIB files are used for SNMP remote management and consist of Object Identifiers (OID’s). Each
OID is a node that provides remote management of a particular function. A MIB file is a tree of
nodes that is unique to a particular device. The following MIB files are associated with the KPA:
MIB File/Name Description
FW-0000141-.mib
Comtech EF Data
Root MIB file ComtechEFData MIB file gives the root tree for ALL Comtech EF Data SSPA
products and consists of only the following OID:
Name: comtechEFData
Type: MODULE-IDENTITY
OID: 1.3.6.1.4.1.6247
Full
path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).comtechEFData(6247)
Module: ComtechEFData
FW-0000139-.mib
ISSPA MIB
MIB file consists of all of the OID’s for management of the KPA functions
FW-0000140-.mib
ISSPA Traps MIB
Trap MIB file is provided for SNMPv1 traps common for the KPA.
These MIB files should be compiled in a MIB Browser or SNMP Network Monitoring System server.
6.3.2 SNMP Community Strings
The KPA uses community strings as a password scheme that provides authentication before
gaining access to the KPA agent’s MIBs.
In SNMPv1 and SNMPv2c, the community string is sent unencrypted in the SNMP packets.
Caution must be taken by the network administrator to ensure that SNMP packets travel only over
a secure and private network if security is a concern. A packet sniffer can easily obtain the
community string by viewing the SNMP traffic on the network.
The community string is entered into the MIB Browser or Network Node Management software
and is used to authenticate users and determine access privileges to the SNMP agent.
The user defines three Community Strings for SNMP access:
• Read Community
default = public
• Write Community
default = private
• Trap Community
default = comtech