Moving Rings From Module-Level To Hub-Level - 3Com CoreBuilder 5000 User Manual

4-8 C M
ONFIGURING THE ODULE
Example:
Moving Rings from
Module-Level to
Hub-Level
Example:
CB5000> set network token_ring isolated_3 7 mode backplane
The following command enables the mismatch resolution mechanism
on backplane network token_ring_3:
CB5000> set network token_ring token_ring_3
mismatch_resolution enable
Value set to ENABLED.
Use SET NETWORK TOKEN_RING MODE command to toggle entire
rings between isolated (module-level) and backplane (hub-wide) Token
Ring networks. This command is valid for port-switched modules only.
This setting is saved automatically and is not affected by the SAVE or
REVERT commands. This command affects only the specified slot and
cannot be used to isolate every module in the hub.
You can implement each of the 10 available token rings on
CoreBuilder 5000 port-switching media modules either on a backplane
(hub-wide) or an isolated (module-level) network. Use this command
to toggle sets of ports between backplane and isolated. You may only
toggle rings 1 through 10.
You specify a slot number when indicating the isolated network the
command affects. The command only affects the specified slot and
cannot be used to isolate each module in the hub.
The command sequence is:
SET NETWORK TOKEN_RING {network} MODE
Where:
network = token_ring_1 to token_ring_10
ISOLATED {slot} = identifies the isolated network the command
affects
The following command assigns all ports assigned to isolated_3
(module-level ring) in module 7 to token_ring_3 (backplane ring):
isolated_1 {slot} - isolated _11 {slot}
BACKPLANE
ISOLATED {slot}