release level

[albiej]

I have an 81C and cpu 0 has a problem. I don't have the Cpu part# available right now but the cpu consists of a floppy, internal hard dr. and cd drive. My good Cpu assembly has a release 7 level. If my bad CPU zero has to be replaced can any release level be used or does it have to match my good one?

 

[senk1s]

on redundant systems like the 81c , it has to be an exact match ...

 

[Avaya911PLM]

That is correct if you are NOT running Succession 3.0. In this version of the software code all drives are formatted to 6 Gig. and the 'same release level' rule does not apply. If you have 25.40b or lower, you need an EXACT match or you will loos RDUN on the 5th run of the midnight routines when the system does it's RDUN tests.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[albiej]

Ok, so far so good. Here is more info... The Part#'s on both Cpu's are: NT5D61AB Rlse 7. Now am I correct in assuming that the "AB" has to be the same on both Cpu's and the "Rlse 7" also has to match? The sw in pbx is 25.30

 

[albiej]

Bump

 

[albiej]

Thanks for all that replied. My service man's Engineering dept has gone around and around with Nortel Engineers in this matter. The consensus is that it won't matter. Last evening they replaced the NT5D61AB Rlse 7 with an "AB" Rlse 8 and all is well so far. Midnight routines went ok. I will monitor for possible RDUN failures etc for a while.

 

[senk1s]

thats interesting fletch ...do you mean when running succession 3.0 software - you may have 2 different types of CPU on a single redundant switch?

can you direct me to some documentation in that regard?

 

[Avaya911PLM]

I thought we are talking about different revs of the IODUC's not the CP cards.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[johnpoole]

i got lost to fletch, he said cpu but then the contain floppy and hd puts it next door.. i always run a match, it's just as easy to swap both as long as you had to split it anyway

john poole
bellsouth business
columbia,sc

 

[Reusser]

Info from 3.0 GRB
5.1.3 CPP Mixed Disk Drive
The design of the current CP PII processor is to operate with MMDU of same size on
both the cores. The disk redundancy is not supported for MMDU of different sizes.
Replacing the MMDU in a CP-PII system is a difficult operation and frequently involves
downtime. If the system can only operate with two identical MMDUs, and the distributor
only has spares of a different size than that being repaired, both MMDUs have to be
replaced.
With a variety of disk sizes in the field, it is important to allow distributors to replace a
defective MMDU with another MMDU of any size larger than 6 GB to minimize the
downtime and to keep distributors spares inventories down to acceptable levels.
This software feature allows the use of MMDU of any size (not less than 6 GB) in the
CP-PII and allows any combination to be equipped.
There is a parallel hardware modification to the MMDU each time that a change in drive
is required. But this feature is intended to allow these to be independent.
This Feature provides the following:
• Allow the two CPP processors to have different sized MMDU and still provide
full service operation, including CPU switchover operations.
• Permit future changes of disk size to be implemented without further software
changes at that time.
• Permit the MMDU to be changed, even to a different size or to/from a mixed
configuration, without any system down time. This would exclude any downtime
incurred as a result of having to power down an entire Core-Net shelf in order to
gain access to the MMDU.