Alcatel OS6400-48 Hardware User Guide - Page 119

Manual Slot Number Assignment, stack set slot

Get Alcatel OS6400-48 PDF manuals and user guides View all Alcatel OS6400-48 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 119 highlights

Managing OmniSwitch 6400 Series Stacks Slot Numbering Manual Slot Number Assignment To manually assign slot numbers to one or more modules in a stack, use the stack set slot command. This command writes slot information to the boot.slot.cfg file located in a switch's /flash directory. It is this saved slot information that the switch will assume following a reboot. Manually assigning slot numbers can be useful in reordering existing slot numbers in order to create a sequential numbering scheme from the top of the stack to the bottom (or vice-versa). Refer to the following example: Slot 6 - Idle Slot 7 - Idle Slot 8 - Idle Slot 1 - Primary Slot 2 - Secondary Slot 3 - Idle Slot 4 - Idle Slot 5 - Idle This example, taken from page 6-19, shows a stack in which the primary and secondary switches are physically positioned in the middle of the stack. Although the stack will operate normally with this primary and secondary module positioning, it may be preferable for management purposes to have the primary and secondary switches at either the top or the bottom of the stack. For this example, the primary and secondary roles will be assigned to the top of the stack. This is accomplished by entering the following commands: -> stack set slot 6 saved-slot 1 -> stack set slot 7 saved-slot 2 -> stack set slot 8 saved-slot 3 -> stack set slot 1 saved-slot 4 -> stack set slot 2 saved-slot 5 -> stack set slot 3 saved-slot 6 -> stack set slot 4 saved-slot 7 -> stack set slot 5 saved-slot 8 -> reload all Because slot 6 is the top-most switch in the stack, it is reassigned the slot 1 (i.e., primary) position; because slot 7 is located immediately below slot 6, it is reassigned the slot 2 (i.e., secondary) position, etc. Note that the modules were not reloaded one-by-one, even though the stack set slot command provides optional syntax for doing so. Instead, new slot number information is first saved to each boot.slot.cfg file across the stack. The reboot is saved for last in order to avoid duplicate slot numbers within the stack, which would cause unwanted pass-though mode conditions (see page 6-12). OmniSwitch 6400 Series Hardware Users Guide July 2010 page 6-21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
Managing OmniSwitch 6400 Series Stacks
Slot Numbering
OmniSwitch 6400 Series Hardware Users Guide
July 2010
page 6-21
Manual Slot Number Assignment
To manually assign slot numbers to one or more modules in a stack, use the
stack set slot
command. This
command writes slot information to the
boot.slot.cfg
file located in a switch’s /flash directory. It is this
saved slot
information that the switch will assume following a reboot.
Manually assigning slot numbers can be useful in reordering existing slot numbers in order to create a
sequential numbering scheme from the top of the stack to the bottom (or vice-versa). Refer to the follow-
ing example:
This example, taken from
page 6-19
, shows a stack in which the primary and secondary switches are phys-
ically positioned in the middle of the stack. Although the stack will operate normally with this primary and
secondary module positioning, it may be preferable for management purposes to have the primary and
secondary switches at either the top or the bottom of the stack. For this example, the primary and second-
ary roles will be assigned to the top of the stack. This is accomplished by entering the following
commands:
-> stack set slot 6 saved-slot 1
-> stack set slot 7 saved-slot 2
-> stack set slot 8 saved-slot 3
-> stack set slot 1 saved-slot 4
-> stack set slot 2 saved-slot 5
-> stack set slot 3 saved-slot 6
-> stack set slot 4 saved-slot 7
-> stack set slot 5 saved-slot 8
-> reload all
Because slot 6 is the top-most switch in the stack, it is reassigned the slot 1 (i.e., primary) position;
because slot 7 is located immediately below slot 6, it is reassigned the slot 2 (i.e., secondary) position, etc.
Note that the modules were not reloaded one-by-one, even though the
stack set slot
command provides
optional syntax for doing so. Instead, new slot number information is first saved to each
boot.slot.cfg
file
across the stack. The reboot is saved for last in order to avoid duplicate slot numbers within the stack,
which would cause unwanted pass-though mode conditions (see
page 6-12
).
Slot 1 - Primary
Slot 2 - Secondary
Slot 3 - Idle
Slot 4 - Idle
Slot 5 - Idle
Slot 6 - Idle
Slot 7 - Idle
Slot 8 - Idle