devel:device_data_model
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
devel:device_data_model [2007/07/04 08:17] morten fix |
devel:device_data_model [2007/07/04 13:08] (current) morten one more diagram |
||
|---|---|---|---|
| Line 43: | Line 43: | ||
| | Commander | netbox & module | | | Commander | netbox & module | | ||
| | Member | module | | | Member | module | | ||
| + | |||
| Line 48: | Line 49: | ||
| ==== Virtual stacks and clusters ==== | ==== Virtual stacks and clusters ==== | ||
| - | {{devel:virtual_stack.png |Diagram of a virtual stack}}Some vendors provide a way to virtually stack multiple standalone devices by connecting them by their regular ethernet ports. Typically, one device in such a stack is assigned the role of //commander//, while the other devices take the role of //members//. The commander will have an IP address and provide management facilities for the stack as a whole. **BUT**, the commander will not present the stack as a single physical unit to the management station. Each device in this stack operates independently of one another; the commander will allow the management station to communicate with each stack member by addressing them with a modified SNMP community string - in essence relaying SNMP communication between the members and the management station. | + | {{devel:virtual_stack.png |Diagram of a virtual stack}}Some vendors provide a way to virtually stack multiple standalone devices by connecting them by their regular ethernet ports. Typically, one device in such a stack is assigned the role of //commander//, while the other devices take the role of //members//. The commander will have an IP address and provide management facilities for the stack as a whole. **BUT**, the commander will not present the stack as a single physical unit to the management station. |
| - | Stack members can optionally also take each their IP address, but will mostly function fine without one. | + | {{ devel:virtual_stack2.png|Another example of how to connect virtually stacked devices}} Each device in this stack operates independently of one another; the commander will allow the management station to communicate with each stack member by addressing them with a modified SNMP community string - in essence relaying SNMP communication between the members and the management station. Stack members can optionally also take each their IP address, but will mostly function fine without one. |
| 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 ;-) | ||
devel/device_data_model.1183537072.txt.gz ยท Last modified: 2007/07/04 08:17 by morten
Page Tools
