|
From: DeSantos, M. <MDe...@Jo...> - 2025-11-04 23:32:12
|
Hello,
I'm pulling my hair out trying to get netdisco to work again. It's been a great tool for years now, but I recently updated and can't seem to get anything to work anymore. I always had an overlap with the YAML config meaning our switches/firewalls use the same mgmt subnet, but I would use host_group to match the individual firewall IP and a subnet to match the remaining switches. I tried various configurations but each time I failed.
Can someone please review my device_auth, host_group, and discover_only stanza and let me know what I'm missing here. I commented out the SNMP stanza to test SSH/CLI for the firewalls. The debug output returns 'discovery skipped: 10.10.200.220 is not discoverable.
device_auth:
# - tag: 'Extreme'
# version: '3'
# user: 'redacted'
# auth:
# pass: 'redacted'
# proto: 'SHA'
# priv:
# pass: 'redacted'
# proto: 'AES' # Changed from DES to AES for compatibility
- tag: 'Firewalls'
driver: 'cli'
platform: 'PaloAlto'
only:
- 'group:paloalto-firewalls'
username: 'redacted'
password: 'redacted'
ssh_master_opts:
- "-o"
- "StrictHostKeyChecking=no"
# Host groups for access control
host_groups:
paloalto-firewalls:
- 'ip:^10\.(1|3|4|5|6|7|8|9|10|24|42|200)\.200\.210$'
- 'ip:^10\.(1|3|4|5|6|7|8|9|10|24|42|200)\.200\.220$'
# Discovery targets
discover_only:
- group: 'extreme-switches'
device_auth: 'Extreme'
subnet:
- 10.1.200.0/24
- 10.3.200.0/24
- 10.4.200.0/24
- 10.5.200.0/24
- 10.6.200.0/24
- 10.7.200.0/24
- 10.8.200.0/24
- 10.9.200.0/24
- 10.10.200.0/24
- group: 'paloalto-firewalls'
device_auth: 'Firewalls'
hosts:
- 10.10.200.210
- 10.10.200.220
--
Thanks,
Matt
|