18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 195: Community<br />

name within an SNMP<br />

message<br />

Chapter 15: Configuring the SNMP Agent<br />

SNMP and <strong>Sidewinder</strong> <strong>G2</strong><br />

The management station displays a graphical representation <strong>of</strong> a network’s<br />

topology through a Windows-based environment. In general, network<br />

managers can monitor each SNMP node (including the <strong>Sidewinder</strong> <strong>G2</strong>) by<br />

clicking an icon representing each node in the network’s topology.<br />

A management station in the internal or external network can request<br />

information from a managed node’s SNMP agent. The SNMP management<br />

station sends a managed node Get and GetNext SNMP messages to retrieve<br />

node-specific parameters and variables, called objects. The message<br />

response from the managed system provides the SNMP administrator with<br />

information on a node’s device names, status, network connections, etc.<br />

Important: SNMPv1 agents typically allow Get, GetNext, and Set requests from the<br />

management station. However, the <strong>Sidewinder</strong> <strong>G2</strong> SNMPv1 agent does not<br />

support Set requests. This prevents a management system from sending<br />

commands to change variables or parameters in the <strong>Sidewinder</strong> <strong>G2</strong>.<br />

Each managed node can send an unsolicited event notification message,<br />

called a trap, to a management station when it detects certain system events.<br />

For example, you can configure the SNMP agent in the <strong>Sidewinder</strong> <strong>G2</strong> to issue<br />

a trap whenever an unauthorized user tries to read, write, or execute a<br />

protected file on the <strong>Sidewinder</strong> <strong>G2</strong>. (Refer to “<strong>Sidewinder</strong> <strong>G2</strong> SNMP traps” on<br />

page 579 for a list <strong>of</strong> all traps supported by <strong>Sidewinder</strong> <strong>G2</strong>.)<br />

When setting up SNMP management, a network administrator assigns the<br />

management station and the nodes it will manage a community name. As<br />

shown in Figure 195, the community name is in the authentication header in<br />

each SNMP message exchanged between a management station and a<br />

managed node.<br />

VERSION<br />

COMMUNITY<br />

NAME<br />

SNMP COMMAND: GET, GETNEXTREQUEST, ETC.<br />

The SNMP agent treats the community name like a password to validate the<br />

identity <strong>of</strong> a management station. For example, suppose a management<br />

station sends a get request to retrieve information from a managed node’s<br />

SNMP agent. If the community name within the get request is not also used by<br />

the SNMP agent, the agent will not return information to the management<br />

station.<br />

Caution: To increase security on your network, do not use common default names<br />

such as “public” or “private,” which can be easily guessed.<br />

Both the management station and the managed node also contain<br />

Management Information Bases (MIBs) that store information about the<br />

managed objects. Currently, the SNMP agent on <strong>Sidewinder</strong> <strong>G2</strong> supports<br />

465

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!