Ad Widget

Collapse

Looking for better switch discovery

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Evan.Anderson
    Member
    • Jun 2009
    • 42

    #1

    Looking for better switch discovery

    I know that during discovery we have the option to add templates to hosts. I want to perform check SNMPv2-SMI::mib-2.47.1.1.1.1.13.1001 and add a different template based on the received value, so do I need a separate discovery action for each received value? Because the received value could be 1 of many see below:

    some possible values that could be received:
    WS-C3750-48PS-S
    WS-C3750-24PS-S
    WS-C3750-24TS-S

    etc..all the 3750 models.
  • MrKen
    Senior Member
    • Oct 2008
    • 652

    #2
    I haven't tried this but it looks do-able.

    Conf --> Discovery. In 'New check' select SNMPv2 agent, community, and SNMP OID = SNMPv2-SMI::mib-2.47.1.1.1.1.13.1001

    Conf --> Actions. Event source = Discovery
    Create New Action condition: Received value = WS-C3750-48PS-S

    Create Action operation: Operation type = Link to template
    then Select the Template.

    * Create a new action for each possible 'Received value'.

    The theory sounds good!

    MrKen
    Disclaimer: All of the above is pure speculation.

    Comment

    • Evan.Anderson
      Member
      • Jun 2009
      • 42

      #3
      Can I

      Originally posted by MrKen
      I haven't tried this but it looks do-able.

      Conf --> Discovery. In 'New check' select SNMPv2 agent, community, and SNMP OID = SNMPv2-SMI::mib-2.47.1.1.1.1.13.1001

      Conf --> Actions. Event source = Discovery
      Create New Action condition: Received value = WS-C3750-48PS-S

      Create Action operation: Operation type = Link to template
      then Select the Template.

      * Create a new action for each possible 'Received value'.

      The theory sounds good!

      MrKen
      Okay, so I gather that for every switch in a stack, I'd need a separate action right?

      for instance if I had a stack with 3 members and 1 master,
      WS-C3750-48PS-S-1
      WS-C3750-48PS-S-2
      WS-C3750-24PS-S-3
      WS-C3750-48TS-S-4

      the OID's are as follows
      SNMPv2-SMI::mib-2.47.1.1.1.1.13.1001
      SNMPv2-SMI::mib-2.47.1.1.1.1.13.2001
      SNMPv2-SMI::mib-2.47.1.1.1.1.13.3001
      SNMPv2-SMI::mib-2.47.1.1.1.1.13.4001

      There is 3 different model in this example, so would that be 3(models) X 4(switches) = 12 discovery actions & 4 discovery checks?

      Comment

      • MrKen
        Senior Member
        • Oct 2008
        • 652

        #4
        Originally posted by Evan.Anderson
        Okay, so I gather that for every switch in a stack, I'd need a separate action right?

        for instance if I had a stack with 3 members and 1 master,
        WS-C3750-48PS-S-1
        WS-C3750-48PS-S-2
        WS-C3750-24PS-S-3
        WS-C3750-48TS-S-4

        the OID's are as follows
        SNMPv2-SMI::mib-2.47.1.1.1.1.13.1001
        SNMPv2-SMI::mib-2.47.1.1.1.1.13.2001
        SNMPv2-SMI::mib-2.47.1.1.1.1.13.3001
        SNMPv2-SMI::mib-2.47.1.1.1.1.13.4001

        There is 3 different model in this example, so would that be 3(models) X 4(switches) = 12 discovery actions & 4 discovery checks?

        I guess that would depend on how your templates differ. If, for example, all the 48 port switches were to be using the same template, you could do it like the pix below. If that were to be suitable, then you could get away with one Discovery Rule and two Discovery Actions (1 for 24 port switch and 1 for 48 port switch), but of course it depends on the template that you want to link to the host.


        MrKen
        Attached Files
        Disclaimer: All of the above is pure speculation.

        Comment

        Working...