Alarm Configuration

NOTE

If you select an object which is not resident in the device Þrmware, you will receive a ÒSet Failed; ensure variable is readableÓ message when you try to set your alarm by clicking on the Apply button. If you are unsure just which objects are resident on your device, and you Þnd yourself receiving a lot of ÒSet FailedÓ messages, you can use the MIB Tools utility (accessed from the main console window menu bar or from the Chassis View) to determine which objects are and are not part of your deviceÕs Þrmware Ñ simply query the object you are interested in; if the query response comes back empty, the object is not present (make sure you are using the appropriate community name when making a query, or you will get no response).

5.Once you have selected the object you wish to use for your alarm variable, you must assign the appropriate instance value in the Alarm Instance field. Most RMON objects are instanced by the index number assigned to the table in which they reside; for example, if you wish to set an alarm on an object located in an RMON Statistics table, you can determine the appropriate instance by noting the index number assigned to the table that is collecting data on the interface you’re interested in. In the case of the default tables, index numbers often mirror interface numbers; however, if there are multiple default tables per interface, or if additional tables have been created, this may not be true. (Table index numbers are assigned automatically as table entries are created; no two tables — even those on different interfaces — will share the same table index number.)

If you have selected an object from a table which is indexed by some other means — for example, by ring number — you must be sure to assign the instance accordingly. If you’re not sure how a tabular object is instanced, you can use the MIBTree utility (described in the Tools Guide) to query the object; all available instances for the object will be displayed. (Host and matrix table objects — which are indexed by MAC address — require special handling; see the Note which follows this step.)

If you have selected an object which is not part of a table, you must assign an instance value of 0.

You can use the MIB Tree panel to determine which objects are tabular and which are not:

TIP objects which are part of a table will descend from a blue folder (which will have a ÒTÓ on it, and a name which will almost always include the word ÒtableÓ); objects which are not will descend directly from a yellow folder. (Note: There may be one or more yellow folders in between the blue folder which contains the table and the leaf object you wish to use; however, those objects are still part of the table.)

Be sure you define your instance values carefully; if you neglect to set the instance correctly, you will receive the “Set failed; ensure variable is readable” error message when you click the Apply button to set your alarm.

3-18

Advanced Alarm Configuration

Page 116
Image 116
Cabletron Systems 2000 manual Alarm Configuration

2000 specifications

Cabletron Systems was a prominent company in the networking and communications industry during the late 20th century, and by the year 2000, it had established itself as a leader in providing high-performance networking solutions. The company was known for its innovative approach to network architecture and its commitment to delivering reliable products that enabled seamless connectivity in various environments.

One of the primary features of Cabletron Systems in 2000 was its advanced networking technologies, including Local Area Network (LAN) and Wide Area Network (WAN) solutions. The company specialized in developing multi-layer switches that could efficiently manage traffic and deliver high-speed data transfer. Their products were particularly popular in enterprise settings, where network performance and reliability were paramount.

Cabletron's solutions included a range of products, from Ethernet switches to routers, which were designed with scalability and flexibility in mind. This allowed businesses to adapt their networks to accommodate growth, without the need for a complete overhaul of their infrastructure. The company’s Integrated Networking Architecture (INA) was a significant innovation during this period, enabling efficient communication and management of diverse network resources.

Another major characteristic of Cabletron Systems was its commitment to interoperability. The company’s products were designed to be compatible with several industry standards, ensuring that organizations could easily integrate Cabletron solutions into their existing networks. This focus on compatibility helped to foster collaboration among different devices and systems, further enhancing network efficiency.

Security was also a key feature of Cabletron’s offerings in 2000. With growing concerns about data breaches and unauthorized access, the company incorporated advanced security measures into its products. These features included robust authentication protocols, encryption options, and secure management interfaces, which helped safeguard sensitive data during transmission.

Customer support and service were paramount to Cabletron Systems' business model. The company provided extensive resources, including training and technical support, to ensure that customers could maximize the potential of their networking solutions. This dedication to customer satisfaction contributed significantly to Cabletron’s reputation in the marketplace.

In summary, Cabletron Systems in 2000 emerged as a frontrunner in the networking industry, characterized by its innovative technologies, commitment to interoperability, emphasis on security, and strong customer support. Their products and solutions were designed to empower businesses, helping them achieve greater efficiency, scalability, and reliability in their network operations.