includes/definitions/fortiswitch.yaml

os: fortiswitch
text: 'Fortinet FortiSwitch'
type: network
icon: fortinet
mib_dir:
    - fortinet
over:
    - { graph: device_bits, text: 'Device Traffic' }
    - { graph: device_processor, text: 'CPU Usage' }
    - { graph: device_mempool, text: 'Memory Usage' }
discovery:
    - sysObjectID:
        - .1.3.6.1.4.1.12356.106. #FortiSwitch
refactor: Move OS definitions into yaml files (#5189) 2016-12-23 17:53:19 +00:00			`os: fortiswitch`
			`text: 'Fortinet FortiSwitch'`
			`type: network`
			`icon: fortinet`
			`mib_dir:`
			`- fortinet`
			`over:`
			`- { graph: device_bits, text: 'Device Traffic' }`
			`- { graph: device_processor, text: 'CPU Usage' }`
			`- { graph: device_mempool, text: 'Memory Usage' }`
newdevice: Improve Fortinet Fortiswitch detection (#5747) 2017-02-03 03:24:36 -06:00			`discovery:`
refactor: Updated discovery/poller to use numeric sysObjectID (#7922) * refactor: Updated discovery to use a core module for sysDescr/sysObjectID use * final update hopefully * revert changes * more changes + docs * migrated poller to use numerical sysObjectID * more updates for sysObjectID * update any alert rules which might have enterprises. in * moved schema file * small updates * updated getHostOS() * scrut fixes * updated sysObjectId -> sysObjectID * updated sysObjectId -> sysObjectID * updated remainder of sysObjectId -> sysObjectID * another sysObjectId -> sysObjectID * fixed secureplatform test data * Fix tests: $device is not pulled from the database before polling Also, update the db in the core discovery module. 2018-01-07 05:00:47 +00:00			`- sysObjectID:`
device: Always allow empty ifDescr on fortigate (#7547) fixes: #3859 2017-10-25 14:57:18 -05:00			`- .1.3.6.1.4.1.12356.106. #FortiSwitch`