8600 IST between 8691SF & 8692SF managed chassis

[Larryski]

IST / SMLT installation Discussion

I have been requested to configure an IST / SMLT infrastructure between 2 x 8010 chassis
The Chassis have dual SSF modules in each.
My concern however is the SSF are different version i.e 2 x 8691SF in one chassis and  2 x 8692SF
in the other.
Both chassis are running 
software version     : 4.1.4.0,
monitor version      : 4.1.4.0/020
&
software version     : 4.1.4.0
monitor version      : 4.1.4.0

Are you aware of any issues which will prevent this implementation.
Many Thanks
Larry_s

[Michael McNamara]

There should be no issues so long as both switches are running the same software release.

I would advise that you upgrade to 4.1.8.3 software before you create the IST link... and cluster the switches together.

You'll need to be careful with regard to how heavily you load the switches because the 8691SF will top out well before the 8692SF. I would recommend RSMLT in place of VRRP (much easier on the CPU/SFs in terms of performance and scaling).

Good Luck!

[Larryski]

Thank You for your Suggestion and Recommendations.

[Larryski]

Your Recommendation to migrate to ver 4.1.8 has been noted however
I know if an upgrade is required then Ver 5.1.1 / ver 5.1.2 will be requested.
Is there any issue regarding SSF mixed setup which would prevent Ver 5.1.1 / ver 5.1.2
for making a stable IST / SMLT configuration.

Many Thanks

Larry_s

[Michael McNamara]

I'm not sure that the 8691SF is 'supported' in release 5.x software... even if it is you might not want to chance it. You'll find the 4.1.8.3 will put an additional load on the CPU/SF, in addition you'll find that 5.x will put an even more significant load on the CPU/SF.

Good Luck!

[tbigby]

The 8691SF is supported in 5.x, but only with the 256MB memory upgrade kit. The memory upgrade cost an awful lot for what should be some fairly cheap memory, but we thought it best to go for the supported, Nortel certified path.

However, the 8691SF isn't supported in 7.x or presumably any future versions.

We've used 5.0.0.0 and now 5.1.1.1. I haven't noticed a problem in terms of CPU load, but we're not running SMLT or anything advanced across it, just Layer 3 static routing. I don't think I've ever seen it above 10% utilisation.

[Larryski]

Thank You for your assistance
I do not believe i have a 8691SSF with 256Mb memory upgrade
however is there a command i can utilise to determine if the Memory upgrade is installed or not.

Extract from Tech Support
# Slot  5 8691SF   0x200e0100 0x00000000  CPU: CPLD=0  MEZZ=2  SFM: OP=3 TMUX=2 SWIP=3 FAD=1 CF=16
# Slot  6 8691SF   0x200e0100 0x00000000  CPU: CPLD=19 MEZZ=2  SFM: OP=3 TMUX=2 SWIP=3 FAD=1 CF=16

Many Thanks
Larry_s

[Michael McNamara]

You should be able to see the amount of memory you have from a "show sys perf" command

ERS-8610:5# show sys perf

                      CpuUtil: 10%
             SwitchFabricUtil: 0%
        OtherSwitchFabricUtil: 0%
                   BufferUtil: 0%
                    DramSize: 256 M
                    DramUsed: 54 %
                    DramFree: 118886 K



Good Luck!

[Larryski]

Many Thanks
Moving forward with upgrade to Ver 4.1.8.3
The modules within the chassis are
8608SX ,8616GTE, 8648TXE, 8616SXE, 8608SXE
I see there is no specific .dld file for these modules so can i assume these modules are covered by the
p80a4183.img

The sys perf indicated 256M on each SSF module
Many Thanks
Larry_s
 

[Michael McNamara]

You are correct in that all the software necessary to run the E and M modules are includes in the Agent (p80a4183.img) and/or SuperMezz (p80m4183.img) software. It's only the R and RS modules that require an additional software (p80j4183.dld) file.

I would urge that you review the 4.1.8.3 software release notes... you will need to bring both switches down at the same time to perform the upgrade. This is usually not the case but because of the redesigned IST/SMLT architecture there's no way around it. You'll actually find that the switch will admin-down (disable) the ports until it can establish a connection on the IST link.

Good Luck!

[Larryski]

Thanks for The Admin down info.
If an IST is required then should the IST be created with old 4.1.4 version prior to upgrade.
Then Upgrade and reconnect IST. Is there any other issues regarding exiting config and upgrade.
I have read release notes, slight concerns re Admin down, can admin down be over ridden re CLI ( console )
in event of continous lockup ( Admin Down )

Once old IST has been established can it be edited without Admin down issue affecting 2 x chassis.

Many Thanks

Larry_s
 

[Michael McNamara]

It goes like this.. you will upgrade one switch (and reboot), and then immediately you will upgrade the other switch (and reboot). For the time it takes the two switches to complete their reboot the network will be down. There are no ways around this. The switch will admin-down all ports as a protection mechanism to prevent the differing software releases from mistakenly trying to work with each other. When the first switch recovers it will take down all ports but the IST ports and will wait for the second switch and for the IST to establish. Once the IST establishes it will admin-up all ports.

In the upgrades I've completed I've found that you should just start the upgrade and keep plowing away and it, don't waste time to watch the process and/or check things. This is especially true if you have dual CPU/SFs. When you upgrade the standby the switch may act a little weird, ignore it and upgrade the primary CPU/SF. The switch will fail-over to the standby CPU/SF. Then go on to the next switch.

Good Luck!

[Larryski]

Many Thanks
I will send update when all is complete

larry_s