Enstore Big A Switch Help
Overview
The Big A Switch page shows the Enstore MIB (
Management Information Bases) information as a shortcut table. The MIB
information is updated by the enstore Big A Switch agent. The shortcut
table contains the links to the MIB information for each of the MIB groups,
the links to the node information and the link to the information of the
thresholds.
The requirements of the
Big A Switch agent:
-
updating MIB by snmpwalk().
-
updating the node dictionaries by self-define functions.
-
updating the html files which can be posted on enstore
web page.
-
checking the MIB such as tcp, udp, ip, icmp, snmp
group objects, checking the node values and sending the events and corresponding
statistics to the NGOP Central Server if any object value reaches the corresponding
threshold.
The Functions of the MIB
Groups and the Nodes:
-
The system group includes configuration information
that pinpoints what the device is, where it is, and who to call when something
goes wrong.
-
The tcp group lets a management application
check up on some TCP configuration value such as the top limit on the number
of concurrent tcp connections that a system can handle.
-
The udp group tracks traffic and errors.
-
The icmp group consists of counts of
every type of incoming and outgoing ICMP message.
-
The snmp group tracks everything and counts
SNMP traffic and errors. Especially, the snmp group tracks the number of
incoming and outgoing gets, sets, responses, and traps, and counts various
errors, such as attempts to read nonexistent variables.
-
The ip group covers the configuration and
management needs of hosts and routers.
-
There are several nodes to be monitored in Big A
Switch. The management information includes configuration information,
the status of the interface, incoming and outgoing traffic statistics,
counts of various kinds of errors, separate counts of broadcast and
multicast traffic, variables that fire off a test and record the test results
and the complete set of physical addresses for which an interface will
absorb traffic.
The Thresholds for the Monitored Objects:
Node Color
|
Arrow Color
|
State of Node
|
SevLevel of Node
|
Description(Threshold)
|
Red
|
-
|
0 (Bad)
|
-
|
Node is down (Too bad) or value reaches the
red threshold.
|
Green
|
Red
|
1 (Good)
|
6
|
|
Green
|
Blue
|
1 (Good)
|
5
|
There is an error in the node
|
Green
|
Orange
|
1 (Good)
|
4
|
Node value reaches the orange threshold.
|
Green
|
Yellow
|
1 (Good)
|
1
|
Node value reaches the yellow threshold.
|
Green
|
-
|
1 (Good)
|
0
|
Node works good.
|
Extending the Big A Switch Agent:
-
If you want to add a new node in Big A Switch to
monitor, the following must be done:
1.go to the file named $ENSTORE_DIR/ngop/node_init.py,
2. add the node key, node NAME, node
PRODuct state, node CABLE number and node ORDER number in the node
dictionary named node_d to initialize the node.
-
If you want to add a group of MIB variables to monitor,
do the following:
1. go to the agent file named $ENSTORE_DIR/ngop/basAgent.py
,
2. define a list that lists the variables,
3. call the functions get_mib_info() and
setTable()
to get the MIB information,
4.save the initiation of the group dictionary
as the offset,
5.add the group name in the list named meNames,
and
6.add the corresponding contents of checking
information in the checkNode() function.
-
To run this new configuration agent, do the following
steps:
1. setup ngop
2. setenv PYTHONPATH $PYTHONPATH":$NGOP_DIR/ma"
or
export PYTHONPATH=$PYTHONPATH":$NGOP_DIR/ma"
3. python $ENSTORE_DIR/ngop/basAgent.py &
Legal
Notices