devel:device_data_model
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
devel:device_data_model [2007/07/03 19:44] morten added data model mapping tables |
devel:device_data_model [2007/07/04 07:48] morten some ideas for future changes |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| | Commander | netbox & module | | | Commander | netbox & module | | ||
| | Member | module | | | Member | module | | ||
| + | |||
| Line 52: | Line 53: | ||
| HP has many products that stack in this way, they call it HP Switch Stacks. Some Cisco devices also support this type of stacking, but they call it //clustering//. According to Cisco documentation, physical 3750 switch stacks can also participate in switch clusters, making the chaos complete ;-) | HP has many products that stack in this way, they call it HP Switch Stacks. Some Cisco devices also support this type of stacking, but they call it //clustering//. According to Cisco documentation, physical 3750 switch stacks can also participate in switch clusters, making the chaos complete ;-) | ||
| - | NAV does not currently support Cisco Clustering (NAV 3.2). | + | NAV does not currently support Cisco Clustering (NAV 3.2). If a cluster is added to NAV, NAV will only see the commander device of the cluster. For more information about Cisco Clustering, please go to [[http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/12119ea1/3750scg/swclus.htm|this page on Cisco's web site]]. |
| Line 58: | Line 59: | ||
| | Commander | netbox & module | | | Commander | netbox & module | | ||
| | Member | module | | | Member | module | | ||
| + | |||
| + | |||
| + | ===== Future changes ===== | ||
| + | |||
| + | The way in which NAV supports HP switch stacks today is a bit contrived (read: hackish), and is, IMNSHO, implemented at the wrong code layer. | ||
| + | There are some ideas to change the way NAV models virtual stacks, which would also make it easier to implement support for Cisco Clustering. These ideas concern themselves with modelling the members of such stacks as automatically generated netboxes with a dependency on the commander netbox. This will enable NAV to view these members for what they are: Operationally independent devices, who happen to share an IP address with another device, but with a different SNMP community. | ||
| + | |||
| + | Administratively, one still wishes to view a virtual stack as a whole, which means the bulk of changes would be in the web user interface to make sure these stacks are presented mostly as before. | ||
| + | |||
| + | These ideas aren't fully fleshed out yet, but more work will be put into that around late August 2007. | ||
devel/device_data_model.txt ยท Last modified: 2007/07/04 13:08 by morten
Page Tools
