Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Clocking Issue?
- Thread starter tomtx
- Start date
Can you post more detail about the 6F SCG 1 error? Not familiar with that - but we have had our share of clocking issues. One was that the Alternate CPPM was trying to 'steal' clocking from our primary CPPM 
I can try to help you out if you can post what you read about the error.
I can try to help you out if you can post what you read about the error.
- Thread starter
- #3
I did a google search on the issue and this is then only hit:
This is where i got that it is a clocking issue. As for the message, it is being displayed on the display of my CPPIV. We do have a primary and alternate CPPIV (processor) but only one CPPM (SS).
You are dealing with a newb so bare with me.
This is where i got that it is a clocking issue. As for the message, it is being displayed on the display of my CPPIV. We do have a primary and alternate CPPIV (processor) but only one CPPM (SS).
You are dealing with a newb so bare with me.
Okay well if you go to LD 135 and issue a stat CPU what do you get? Also do a stat elnk in LD 137. Finally do a stat serv in Ld 117 - maybe some link is down or something like that. I tried to look in docs and couldn't track your particular error down.
>ld 135
CCED000
.stat cpu
cp 0 8 PASS -- ENBL
SYSTEM STATE = REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 14
VERSION = May 23 2007, 00:18:36
Side = 0, DRAM SIZE = 1024 MBytes
CP[0] located at IPMG [4 0 8]
cp 1 9 PASS -- STDBY
SYSTEM STATE = REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 14
VERSION = May 23 2007, 00:18:36
Side = 1, DRAM SIZE = 1024 MBytes
CP[1] located at IPMG [8 0 9]
>ld 135
CCED000
.stat cpu
cp 0 8 PASS -- ENBL
SYSTEM STATE = REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 14
VERSION = May 23 2007, 00:18:36
Side = 0, DRAM SIZE = 1024 MBytes
CP[0] located at IPMG [4 0 8]
cp 1 9 PASS -- STDBY
SYSTEM STATE = REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 14
VERSION = May 23 2007, 00:18:36
Side = 1, DRAM SIZE = 1024 MBytes
CP[1] located at IPMG [8 0 9]
- Thread starter
- #5
Looks to be the same issue that this guy had here but never got answered.
It is being displayed on the SYS UTIL card. I ran what you recommended and all links are up and online.
It is being displayed on the SYS UTIL card. I ran what you recommended and all links are up and online.
Well if everything is clocking properly you can discount it as a cosmetic issue with the display but that seems like a Nortel cop-out 
Do you have any apparant system issue due to it?
I looked at our CS1000e and could not find a System Utility card and when searching Nortel and parts online it seems to be a voicemail card? Strange since you say it is on the CPPIV - we have CPPMs so does your CPPIV also say SysUtil on it? That seems confusing.
Do you have any apparant system issue due to it?
I looked at our CS1000e and could not find a System Utility card and when searching Nortel and parts online it seems to be a voicemail card? Strange since you say it is on the CPPIV - we have CPPMs so does your CPPIV also say SysUtil on it? That seems confusing.
- Thread starter
- #7
No apparent issues with the system. Everything seems to be running fine. Perhaps this message has always been there? but i don't think so.
The sysutil card actually sits right next to the cppiv card. it has a little display screen on the front that displays the cp status/health (which is good) and this error message.
The sysutil card actually sits right next to the cppiv card. it has a little display screen on the front that displays the cp status/health (which is good) and this error message.
Okay - what else is the card used for?? If nothing I don't really see the point because you should be running a health report on your system every morning
Anyway, my first step would be to disable the card, back it out of the system, wait 10 seconds, and push it back in - then re-enable. This is because I would be curious if it is a cosmetic issue with the LED display that has not cleared. If it comes back in the same state I would likely try an INI next to see if it will clear or generate another message. But if you system is touchy like ours is that may not be the best plan of action
Sorry that I haven't heard about that particular error since we have CPPM and not CPP4. The only other question I would have is when was this system installed and have you done any work lately before you 'noticed' the error. All about issue tracking now really.
Anyway, my first step would be to disable the card, back it out of the system, wait 10 seconds, and push it back in - then re-enable. This is because I would be curious if it is a cosmetic issue with the LED display that has not cleared. If it comes back in the same state I would likely try an INI next to see if it will clear or generate another message. But if you system is touchy like ours is that may not be the best plan of action
Sorry that I haven't heard about that particular error since we have CPPM and not CPP4. The only other question I would have is when was this system installed and have you done any work lately before you 'noticed' the error. All about issue tracking now really.
bhassell2000
Technical User
I am pretty sure the sys util card is where the security id dongle is located
Thanks,
Buddy
Linked in Profile
Thanks,
Buddy
Linked in Profile
- Status
Similar threads
- Locked
- Question
