Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution

fault-monitor profile

This thread has been viewed 10 times
  • 1.  fault-monitor profile

    Posted Aug 18, 2022 02:35 AM

    Hello Aruba Community,

    I have got a bunch of "6300M 48SR5 CL6 PoE 4SFP56" and 6300F 24G CL4 PoE 4SFP56 Switches and I would like to enable a fault-monitor profile on every access port.

     

    Is it wise to enable a fault-monitor profile on every access Port by default, or is it a tool I should just enable for trouble shooting?

    Is there may be a performance issue when enabling a fault-monitor profile on every access port?


    Firmware version on the switch: 10.07.0061

    Default configuration on the Access Port:

        no shutdown

        qos trust dscp

        rate-limit broadcast 100 pps

        rate-limit multicast 100 pps

        description NAC

        no routing

        vlan access 1250

        spanning-tree bpdu-guard

        spanning-tree port-type admin-edge

        loop-protect

        port-access onboarding-method concurrent enable

        aaa authentication port-access allow-cdp-bpdu

        aaa authentication port-access allow-lldp-bpdu

        aaa authentication port-access client-limit 8

        aaa authentication port-access preauth-role noaccess

        aaa authentication port-access reject-role noaccess

        port-access allow-flood-traffic enable

        aaa authentication port-access dot1x authenticator

            reauth

            enable

        aaa authentication port-access mac-auth

            reauth

            enable

        client track ip update-interval 60

     

    fault-monitor profile:

    fault-monitor profile PORT_ERRORS

        excessive-broadcasts

        excessive-link-flaps

        excessive-jabbers

        excessive-fragments

        excessive-crc-errors

        excessive-tx-drops

     

    May thanks

     

    Thomas Odermatt