{'fraction_non_alphanumeric': 0.015060240963855422, 'fraction_numerical': 0.0, 'mean_word_length': 5.042424242424242, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Embedding RMON in large LAN switches

A remote network monitoring management (RMON) agent monitors all traffic on a network segment. In a switched LAN, the only device where all traffic can be seen is the LAN switch. Thus, the most appropriate place to insert an RMON probe is in the LAN switch. In this article issues in implementing various RMON groups in a LAN switch are studied, and some approaches are proposed. The centralized solution turns out to be impractical because it is prohibitively expensive. A distributed design is presented that is suitable for implementation on multiprocessor switches. A simple analytical model is used to compare the alternatives. We investigate empirically the cost of performing typical filtering operations in an operational network. This shows that reverse filtering is often much more computationally efficient than forward filtering. We show that the distributed design can provide full RMON capability on all ports simultaneously at affordable cost.