CS1Ke Expansion/Update

[telebub]

I installed a CS1ke Rls 7.5 back in 2011. It has 4 MG1010 cabinets, the main cabinet having a CPMGS card with the other 3 cabinets having MGC cards.

We are adding a 5th cabinet and I thought I would take this opportunity to update all the service updates/patches since this system hasn't been touched in 3 years.

As someone who primarily works on TDM Option 11-81, I don't mess with these "e" systems too often so I thought I would ask for some recommendations on performing these updates.

I've pulled an ISSP and obtained the delta for a deplist refresh on the Call Server. I've pulled the latest SU for the Linux Base. I'm a little fuzzy when it comes to the MGC/DSP cards. Could someone provide recommendation on what I need for those?

Any other suggestions are welcome. Thanks!

 

[KCFLHRC]

The MGC cards and the daughterboards will pull their loadware from the Call Server. You can print a PSWV in ld 22 and paste that into the MIRCC site similar to how you did the MDP ISSP Delta. You do the MGC loadware through EM. Then reboot the MGC cards and they wil pull the new loadware. The Linux has a similar tool also for updating the Service Pack.

 

[telebub]

Here's my PSWV but I don't see on ESPL where to run it in the MIRCC.

PSWV VERSION: PSWV 100+
LCRI:
VERSION NUMBER: AA02
XNET:
VERSION NUMBER: AC23
XPEC:
VERSION NUMBER: AC43
FNET:
VERSION NUMBER: AA07
FPEC:
VERSION NUMBER: AA08
MSDL:
VERSION NUMBER: AJ73
SDI:
VERSION NUMBER: AH51
DCH:
VERSION NUMBER: AA72
AML:
VERSION NUMBER: AK81
BRIL:
VERSION NUMBER: AK83
BRIT:
VERSION NUMBER: AK82
MISP:
VERSION NUMBER: AJ71
BRSC:
VERSION NUMBER: AJ71
BBRI:
VERSION NUMBER: AH54
PRIE:
VERSION NUMBER: AA87
BRIE:
VERSION NUMBER: AK89
ISIG:
VERSION NUMBER: AA33
SWE1:
VERSION NUMBER: BA53
UKG1:
VERSION NUMBER: BA51
AUS1:
VERSION NUMBER: BA49
DEN1:
VERSION NUMBER: BA48
FIN1:
VERSION NUMBER: BA49
GER1:
VERSION NUMBER: BA54
ITA1:
VERSION NUMBER: AA54
NOR1:
VERSION NUMBER: BA49
POR1:
VERSION NUMBER: BA49
DUT1:
VERSION NUMBER: BA50
EIR1:
VERSION NUMBER: BA49
SWI1:
VERSION NUMBER: BA53
BEL1:
VERSION NUMBER: BA49
SPA1:
VERSION NUMBER: BA51
NET1:
VERSION NUMBER: BA48
FRA1:
VERSION NUMBER: BA52
CIS1:
VERSION NUMBER: BA48
ETSI:
VERSION NUMBER: BA48
E403:
VERSION NUMBER: BA07
N403:
VERSION NUMBER: BA05
JTTC:
VERSION NUMBER: AC08
TCNZ:
VERSION NUMBER: AA13
AUBR:
VERSION NUMBER: AA14
AUPR:
VERSION NUMBER: AA04
HKBR:
VERSION NUMBER: AA06
HKPR:
VERSION NUMBER: AA08
SING:
VERSION NUMBER: AA15
THAI:
VERSION NUMBER: AA07
NI02:
VERSION NUMBER: AA26
T1IS:
VERSION NUMBER: AA10
T1ES:
VERSION NUMBER: AA09
ESGF:
VERSION NUMBER: AC30
ISGF:
VERSION NUMBER: AC31
ESGFTI:
VERSION NUMBER: AC29
ISGFTI:
VERSION NUMBER: AC31
INDO:
VERSION NUMBER: AA06
JAPN:
VERSION NUMBER: AA16
MSIA:
VERSION NUMBER: AA04
CHNA:
VERSION NUMBER: AA04
INDI:
VERSION NUMBER: AA03
PHLP:
VERSION NUMBER: AA02
TAIW:
VERSION NUMBER: AA03
EAUS:
VERSION NUMBER: AA02
EGF4:
VERSION NUMBER: AC14
DCH3:
VERSION NUMBER: AA10
PUP3:
VERSION NUMBER: AA14
T1E1:
VERSION NUMBER: AA19
DITI:
VERSION NUMBER: AA40
CLKC:
VERSION NUMBER: AA20
3902:
VERSION NUMBER: DA84
3903:
VERSION NUMBER: DA91
3904:
VERSION NUMBER: DA94
3905:
VERSION NUMBER: DA94
MGC, MGX and MGS:
CSP VERSION: MGCC CD01
MSP VERSION: MGCM AB01
APP VERSION: MGCA BA07
FPGA VERSION: MGCF AA18
BOOT VERSION: MGCB BA07
DSP1 VERSION: DSP1 AB03
DSP2 VERSION: DSP2 AB03
DSP3 VERSION: DSP3 AB03
DSP4 VERSION: DSP4 AB04+
DSP5 VERSION: DSP5 AB04+
UDT VERSION NUMBER: AA42

 

[telebub]

Wait, just found it...

 

[telebub]

Here are the results and I've downloaded each loadware file. Do I just copy these to a specific location on the Signaling Server?

OLD NEW
MGCCCD01 MGCCCD05

MGCMAB01 MGCMAB02

MGCABA07 MGCABA15

MGCFAA18 MGCFAA22

MGCBBA07 MGCBBA15

DSP1AB03 DSP1AB07

DSP2AB03 DSP2AB07

DSP3AB03 DSP3AB07

DSP4AB04 DSP4AB07

DSP5AB04 DSP5AB07

UDTCAA42 UDTCAB25

It also says install T1E1AA19 for TMDI issue

 

[KCFLHRC]

You do it through the patch manager in EM. You basically upload them then activate them. You are limited to 5 or so at a time if I remember right. Might be 7. Keep in mind that when the MGC card see's the loadware mismatch it will automatically try and upgrade the card after a reboot. Or you can invoke it I believe in LD 143. I usually just reboot them. It will only do one at a time and it takes about 15 minutes per MGC card.

 

[telebub]

Cool, thanks!

 

[telebub]

One more question KC. I rarely get into this system but I've been it a few times today getting my ducks in a row and I'm seeing this constantly.

ELAN009 ELAN 0 host IP=137.135.128.200 disabled, write to socket
fail due to far end disconnect or Ethernet problems

ELAN014 ELAN 0 host IP=137.135.128.200 is enabled

And when I login, it's logging me in as an emergency account. I also cannot browse to UCM. I can putty to it and get the login screen and when I enter the credentials, it just sits there and never gives me a command prompt. I've been waiting for several minutes so far.

Any thoughts? Reboot?

 

[KCFLHRC]

My guess is 137.135.128.200 is an MGC card. You can prt the IPMG in LD 117 and see what that IP adddress is. Sounds like it is bouncing. The Emergency account thing is because the Call Server isn't registered to the Primary Security Server. Since you cant browse to UCM I would suspect that it is not working properly or at all. Possibly a reboot of your Primary security Server is in order.

 

[telebub]

Here's my MGCs. Looks like 137.135.128.200 is the Call Server/Signaling Server

=> prt ipmg
IPMG IP Address Zone Type
004 0 137.135.128.210 1 MGS
008 0 137.135.128.211 1 MGC
012 0 137.135.128.212 1 MGC
016 0 137.135.128.213 1 MGC

 

[KCFLHRC]

Well your UCM is going to be on that CPMGS card as your Primary Security Server.

 

[telebub]

FYI, I went to site Wednesday planning to reboot the system that night. While there, I performed an EDD and took the USB stick out to copy the backup to my laptop for an external copy. I placed the USB back into the card and from that point on, the Primary Security Server has been working fine. I guess the USB stick had it hosed up.

I plan on another trip to site next Saturday to perform a deplist refresh, update the media gateway loadware, and update the SU on the Signaling Server. Would you recommend any other updates?

Also, I've always performed SU installation/updates via WinSCP and command line. Can I copy the media gateway loadware using that method rather than EM?

 

[KCFLHRC]

I would not do a Linux Service Pack update via command line. Not a good idea and not supported from what I have been told. The loadware has to be done through EM, I know of no other way. I have been told that if you do the Linux SP through command line it can break the machine beyond repair and require a reinstall of the Linux. I have always done the 3 base patches through WINSCP and Command line but have always done the SP through EM.

 

[telebub]

10-4, thanks!

 

[telebub]

Ok, so I'm browsing around trying to get my bearings and looks like 3 locations for patching:

Linux Base Manager

Software​

​

Applications​

​

Patches​

Elements

CS1000 Services​

​

Patches​

Element Manager

Software​

​

Call Server PEPs​

​

Loadware PEPs​

I was planning on performing the deplist refresh via LD 143 like always do in CS1000m-MG. Can you provide a Cliff's version as to where I would upload the MGC loadware files and the SU for Linux?

 

[telebub]

*Cliff's Notes version*

 

[mikepbx1]

Just to throw in my 2 cents, I ALWAYS patch from the command line!

Linux - SFTP the files over to the following directories:

/var/opt/nortel/patch - upload Service Updates (SUs) here...
/var/opt/nortel/patch/sp - upload Service Packs (SPs) here...

Use pload <patchname> each patch file, and pins --all to install and apply the SU's all at once.

Use spload <filename.zip>, followed by spins to install.

Use pstat and spstat to see which service updates/pack are in service..

To update the loadwares from the the command line, copy the .LW files onto a CF (using a PC), and put the CF in the Call Server RMD slot. Make sure your cores are joined (if HA) and in the security domain.

1. Log into pdt on the call server (UCM account username and password)
2. Then type cd /cf2, type ll and you should see the loadware files
3. One file at a time, copy the loadware in with copy <filename> /u/loadware
4. Use lwload <filename> [all] and lwinst <handle> [all]
5. lwstat shows status of loadware patches on the call server.
6. Enter LD 143, upgmg stat will show you if any MGC's require an upgrade.

http://pbxbook.com

 

[telebub]

Thanks Mike. Seems like I would see all the loadware files in u/loadware but all I see is dsp4ab04.lw and dsp5ab04.lw as patch handles 0 and 1. Currently the MGCs indicate they don't need upgrading but I haven't loaded the new loadware files yet.

Again, current pswv shows:

MGC, MGX and MGS:
CSP VERSION: MGCC CD01
MSP VERSION: MGCM AB01
APP VERSION: MGCA BA07
FPGA VERSION: MGCF AA18
BOOT VERSION: MGCB BA07
DSP1 VERSION: DSP1 AB03
DSP2 VERSION: DSP2 AB03
DSP3 VERSION: DSP3 AB03
DSP4 VERSION: DSP4 AB04+
DSP5 VERSION: DSP5 AB04+
UDT VERSION NUMBER: AA42

I think once I copy the new loadware files into the u/loadware directory, load them, and install them, the upgmg stat command will then show the MGCs need to be upgraded. Sound right?

 

[mikepbx1]

Yes, that sounds right
Good luck!

http://pbxbook.com