xStack
2.CS’s must change their role to CaS and then to MS, to become a MS of a SIM group. Thus the CS cannot directly be converted to a MS.
3.The user can manually configure a CS to become a CaS.
4.A MS can become a CaS by:
a.Being configured as a CaS through the CS.
b.If report packets from the CS to the MS time out.
5.The user can manually configure a CaS to become a CS
6.The CaS can be configured through the CS to become a MS.
After configuring one switch to operate as the CS of a SIM group, additional switches may join the group by manually configuring the Switch to be a MS. The CS will then serve as the in band entry point for access to the MS. The CS’s IP address will become the path to all MS’s of the group and the CS’s Administrator’s password, and/or authentication will control access to all MS’s of the SIM group.
With SIM enabled, the applications in the CS will redirect the packet instead of executing the packets. The applications will decode the packet from the administrator, modify some data, and then send it to the MS. After execution, the CS may receive a response packet from the MS, which it will encode and send it back to the administrator.
When a CaS becomes a MS, it automatically becomes a member of the first SNMP community (include read/write and read only) to which the CS belongs. However if a MS has its own IP address, it can belong to SNMP communities to which other switches in the group, including the CS, do not belong.
The
Command | Parameters |
enable sim |
|
|
|
disable sim |
|
|
|
show sim | {[candidates {<candidate_id |
| |
|
|
reconfig | [member_id <value |
|
|
config sim_group | [add <candidate_id |
| <member_id |
|
|
config sim | [{[commander {group_name <groupname 64> candidate] |
| dp_interval <sec |
download sim_ms | [firmware configuration] <ipaddr> <path_filename> |
| {[members <mslist |
upload sim_ms | <ipaddr> <path_filename> <member_id |
configuration |
|
|
|
Each command is listed, in detail, in the following sections.
241