Booting the Switch
ARX
®
6000 Hardware Installation Guide
7 - 7
differences between replacing a single switch and replacing a member of a
redundant pair is that for a single switch, a re-import is required at the
appropriate point during configuration. Since with a single switch
installation, the configuration is not saved on a backup switch, you have to
manage what you do with these key pieces of configuration data
prior
to the
switch’s failing.
Before You Begin: Verifying Hardware Compatibility
The replacement switch’s hardware must match that of the failed switch. At
the end of the switch replacement, you will run the failed switch’s
running-config on the replacement switch. The running-config includes slot
numbers for the modules, so the new switch must have its modules in the
same slots as its predecessor. Before you begin the replacement process,
verify that the replacement switch has all of its ASMs and NSMs in the
same positions as the failed switch.
Choosing Switch Replacement
The initial-boot script asks if this is a switch replacement. Answer
yes
to
invoke the questions that are required to replace the failed switch. For
example,
...
A
switch
replacement
requires
additional
configuration
questions.
6.
Are
you
doing
a
switch
replacement?
in
the
format
'yes'
or
'no'.(default=no)
#
yes
Matching the Private Subnet
The next set of questions ask for the switch’s
private subnet
, the
private
VLAN
for that subnet, and the VLAN for a private
metalog subnet
. If the
failed switch was in a redundant pair and/or RON network, the private
subnets of the replacement switch should match those of the switch that
failed. Each ARX
®
uses its private subnet for communication with other
ARX
®
es in the same Resilient-Overlay Network (RON) and/or the switch’s
redundant peer. All private subnets in the RON and/or pair are carried by the
same VLAN. This private VLAN, and the separate metalog VLAN, must be
reserved for ARX
®
traffic only.
The private-subnet and VLAN information appears at the top of a the failed
switch’s
show running-config
output. For example, this is the top of a
running-config file from a failed switch. The private-subnet information is
highlighted in bold text:
;
ARX
‐
6000
;
Version
5.02.000.12535
(Feb
5
2010
18:16:05)
[nbuilds]
;
Database
version:
502000.21
;
Generated
running
‐
config
Sun
Feb
14
01:44:06
2010
;
System
UUID
3d17e8ce
‐
571e
‐
11dc
‐
9852
‐
ef323fbb290f
;
ip
private
vlan
internal
1008
metalog
1009
subnet
169.254.17.0
255.255.255.0
;
terminal
character
‐
set
unicode
‐
utf
‐
8
;=================================
vlan
==================================
config
Summary of Contents for ARX 6000
Page 1: ...ARX 6000 Hardware Installation Guide 810 0001 00 ...
Page 2: ......
Page 5: ...Table of Contents ...
Page 6: ......
Page 10: ...Table of Contents x ...
Page 12: ......
Page 22: ...Chapter 1 1 12 ...
Page 24: ......
Page 30: ......
Page 36: ...Chapter 3 Chassis Hardware 3 8 ...
Page 38: ......
Page 46: ......
Page 52: ......
Page 66: ......
Page 80: ......
Page 87: ...A Cable Connectors ARX 6000 Connectors Console Connector and Pinouts SFP Optical Connector ...
Page 88: ......
Page 92: ...Appendix A Cable Connectors A 6 ...
Page 94: ......
Page 100: ...Appendix B Removing and Replacing FRUs B 8 ...
Page 101: ...Index ...
Page 102: ......