Dell Force10 MXL Blade 매뉴얼 - 페이지 23
{카테고리_이름} Dell Force10 MXL Blade에 대한 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. Dell Force10 MXL Blade 27 페이지. 10/40gbe blade switches
Dell Force10 MXL Blade에 대해서도 마찬가지입니다: 시작하기 매뉴얼 (38 페이지), 애플리케이션 노트 (6 페이지), 사양 (2 페이지)
페이지 인쇄
Stacking Dell Force10 MXL 10/40G Switches
Proceed to copy the file [confirm yes/no]: yes
!
9582 bytes successfully copied
Synchronizing data to peer Stack-unit
!!!!
....
FTOS#reload
Once the reload has completed, unplug stacking cables from all ports where stacking was removed.
Renumbering stack units
Renumbering a Master, Standby or member unit, requires the stack-unit renumber command and a
reload of one or more switches:
Renumbering the Master switch requires a reload of the entire stack
Renumbering the Standby switch only requires that switch to reload, but a different member
switch is elected as the new Standby
Renumbering a member switch requires a reload of that switch only
Renumbering any unit in the middle of a daisy-chain topology stack may require a stack-split
and subsequent stack-merge to occur
Renumbering a switch to a number already assigned to another stack unit results in following
error message:
"Renumbering will reset the unit. Warning: Interface configuration for current unit will be
lost! Proceed to renumber [confirm yes/no]:"
Use the following command to renumber:
FTOS#stack-unit 1 renumber 5
Renumbering will reset the unit. Proceed to renumber [confirm yes/no]:
If the new number which we want to assign is already used by an existing member of the stack, the
below error will occur.
FTOS#stack-unit 1 renumber 5
% ERROR: stack unit 5 already exists.
If the new number assignment is already used by a logically provisioned unit in the stack, the below
confirmation message to overwrite is displayed.
FTOS#stack-unit 1 renumber 5
Stack unit 5 has configuration data. Overwrite? [confirm yes/no]:
Caution: Renumbering stack units may hinder management scripts and monitoring software that
collects data based on particular port traffic. Use renumbering with caution when monitoring ports
and be aware that scripts and monitoring parameters may need to be modified.
21