Discovery - Switch Forwarding Rules

Marvin5
Tera Expert

Hi All

 

We've been working with our Network teams and they've provided feedback on the Switch Forwarding Rules created during discovery. Basically they're not required and agreed its just creating extra clutter in our CMDB.

 

I've followed this KB https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0788045 made the sensor is inactive, however when I run a fresh discovery I'm seeing new rules being created.

 

Not sure if i'm missing something?

 

Thanks

Marvin

1 ACCEPTED SOLUTION

Hi @Marvin5 

No, Layer 2 Switching doesn't affect Service Mapping as it's not used in the Service Mapping process; it also doesn't affect Dependency Mapping either, since this is done via Active Process/Active Connection scans on the Server itself during Discovery.

 

If the switch is being discovered using Patterns (i.e. Network Switch) then the actual work is being done by the pattern, not the Probe/Sensor, which is why you're not seeing the process stop.  The Pattern should react to the Config change I suggested.

View solution in original post

4 REPLIES 4

James Hammond
Giga Guru

Hello @Marvin5 

Not sure what version you are currently on, but did you try disabling Network Device Exploration in the Discovery Configuration Console before disabling the Sensor? This normally would kill off the information you're looking for, but if it's just Layer 2 Discovery causing the problem you could always look into this article KB0758421 which shows you how to turn off layer 2 discovery completely.

 

Hi James

 

Oh I didn't do that, it wasn't mentioned in the KB I linked above. Is that something I need to do aswell as disabling the sensor? If I do turn off Network Device Exploration, will that have any impact on our Service Mapping?

 

Thank you

Marvin

Hi @Marvin5 

No, Layer 2 Switching doesn't affect Service Mapping as it's not used in the Service Mapping process; it also doesn't affect Dependency Mapping either, since this is done via Active Process/Active Connection scans on the Server itself during Discovery.

 

If the switch is being discovered using Patterns (i.e. Network Switch) then the actual work is being done by the pattern, not the Probe/Sensor, which is why you're not seeing the process stop.  The Pattern should react to the Config change I suggested.

Hi James

 

Awesome, thank you