Bay Technical Associates 304 Benutzerhandbuch

Seite von 101
Customizing and Managing the BayStack Switches
893-01010-A
3-21
 
information and forward the data to a network management station, where 
network managers perform diagnostic and advanced planning operations. The use 
of SNMP, a common and well-defined protocol, allows the network manager to 
manage any SNMP-compliant device in a multivendor environment.
The Management Information Base (MIB) is a database that stores all of the 
collected statistics and holds them in specific structures. MIB data includes 
configuration and control parameters and statistical data such as the number of 
errors sent and received on a port.
Additional information is collected by the following MIBS and RMONs: 
MIB II
Bridge MIB 
Groups 1, 2, 3, and 9 RMON
— Group 1: Stats (EtherStats Table)
— Group 2: History (history control Table, Ether history control Table)
Only etherStats is supported by history, and the number of buckets is 
limited to 150.
— Group 3: Alarm (alarm Table)
— Group 9: Events (event Table, log Table)
The BayStack switch has a management core that gathers statistics from each of 
the network ports; maintains the MIB; and, when a message for the SNMP 
manager arrives, retrieves the information, puts it into the right form, and sends it 
out the appropriate port.
Access to the switch through SNMP is controlled by community names. 
The community names set for the switch must match those used by the SNMP 
management station for successful communication to occur. The switch uses two 
community names. The “public” community name allows read-only access to the 
device through SNMP. The “private” community name allows read-write access. 
Note: 
EtherStats Alarms and Events entries are saved through power cycle 
of the switch. History entries are not saved through a power cycle.
Alarms, events, and logs are limited to 20 entries each.
89301010.BK  Page 21  Tuesday, June 10, 1997  8:00 PM