This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
devel:tasklist3.3 [2007/09/27 14:15] faltin |
devel:tasklist3.3 [2007/09/27 14:16] faltin |
||
---|---|---|---|
Line 37: | Line 37: | ||
- | ===== MB2: Support auto insertion of types ===== | ||
- | |||
- | ^ Assigned to | Morten Brekkevold | | ||
- | ^ Estimated time | ? hrs | | ||
- | ^ Start date | | | ||
- | ^ Status | | | ||
- | ^ Due for | ? | | ||
- | |||
- | Today when you add a new device of an unknown type you have to manually add the type in | ||
- | edit database. You also have to fill in some less than obvious fields, i.e. frequency. | ||
- | |||
- | Change the type table: | ||
- | * delete the CDP and TFTP fields. A device’s CDP ability can been discovered through the device’s OID support classification, and the TFTP field is not used by anything in NAV. | ||
- | * set 3600 as default for frequency, this should also be shown when manually updating the type table in edit database. | ||
- | |||
- | Make add netbox simpler: | ||
- | * set the typeid=unclassified, leave a more qualified setting to gdd. | ||
- | |||
- | Improve gDD: | ||
- | * when gdd sees a netbox with type unclassified, set the correct type based on sysobjectid. If the sysobjectid does not exist in the type table add it with a best guess type name and type description. | ||
- | * the same mechanism should by used for detected type changes (the ip netbox is replaced with newer equipment of a different type). | ||