Network Operations and Control Wiki
Register
Advertisement

Background: Know: multiple managers, rowStatus, auxiliary Index Recognize:

Anticipates: examples of RMON tables


Up

Previous Next

Down


Sharing RMON tables[]

Arbitration for accessing tables[]

RMON MIBs are gathering information , statistics and local analysize within different tables assigned for each RMON Group . Generally, those tables are classified as are Control and data tables.

The problem appears when multiple managers want to configure the one information simultaneously. For instance, multiple requests are sent to the same row addition together by managers. This leads to occurrence of the conflict. And hence, conflict arbitration is needed within control entries to assist the work of these multiple managers. Moreover, it is set that under the this situation, only the first request is awarded, meanwhile others will view as error.

RMON apply OwnerString and EntryStatus as arbitration functions in order to resolve any conflict that may happened between the management systems.

Column to identify Owner


ownerString Ties the event or Alarm or item to a particular Owner (manager ).

Owner String display the Owner's information such as the IP address , MS name ,his name, adress and telephone number. Entrystatus arbitrates the access for the creation and deletetion of rows shared by multiple managers.

As it is mentioned in this slide EntryStatus is similar to SMIv2 RowStatus , however it was introduced before rowStatus and it has the following states:

1- Valid: Row has active and valid data which is fully opertional and any MS authorized to use this RMON agnet is allowed to use these information that row.

2- creatRequest: the EnteryStatus set to creatRequest when the row of information is not ready and the MS requested to creat a row.[]

3-UnderCreaation : EntryStatus set to underCreation during the time of communication between agent and MS to creation of row . it is used to make alert for the other managers to not use this row.[]

4- Invalid : delete the row[]

Identifying Index column

 Most rows also have an identifying Index column.

Table looking for the first unused index. Because index values may be any valid value in the range and they are chosen by the manager, the agent must allow a row to be created with any unused index value if it has the resources to create a new row.

Some tables in this MIB reference other tables within this MIB. When creating or deleting entries in these tables, it is generally allowable for dangling references to exist. There is no defined order for creating or deleting entries in these tables.


Refernces

Advertisement