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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Siemens Hicom , Hipath /Unify - 24 * 7 online technical support 1
- Thread starter hipath4k
- Start date
- Thread starter
- #2
hipath4K---
Trying to resolve the following problem.
Hipath 4K--Release V4 R4.0.26
System has 8 local LTU shelves.
System has 17 IPDA shelves.
System had 4 APE units--all are offline for months.
This site is to be decomm-ed in the next year or so and things get ignored and written off.
Anyway the main issue is CC-B.
Whenever CC-B is switched online it will not remain active for more that 2-3 minutes.
It restarts hard and goes back to CC-A.
At that point CC-B just restarts forever as standby.
The errors have pointed to RTM, LTUC, HDLC defect pointing to multiple LTUC cards, basically points to everything and nothing.
All of the hardware in the CPCI cabinet has been replaced except the MCM and power supplies.
All of the LTUC cables for CC-A and CC-B have been replaced.
Multiple LTUC cards have been replaced.
I have worked on this product for several years and have never seen this behavior.
Our next idea is to replace the entire CPCI cabinet.
Any thoughts are welcome.
Thanks,
If
Trying to resolve the following problem.
Hipath 4K--Release V4 R4.0.26
System has 8 local LTU shelves.
System has 17 IPDA shelves.
System had 4 APE units--all are offline for months.
This site is to be decomm-ed in the next year or so and things get ignored and written off.
Anyway the main issue is CC-B.
Whenever CC-B is switched online it will not remain active for more that 2-3 minutes.
It restarts hard and goes back to CC-A.
At that point CC-B just restarts forever as standby.
The errors have pointed to RTM, LTUC, HDLC defect pointing to multiple LTUC cards, basically points to everything and nothing.
All of the hardware in the CPCI cabinet has been replaced except the MCM and power supplies.
All of the LTUC cables for CC-A and CC-B have been replaced.
Multiple LTUC cards have been replaced.
I have worked on this product for several years and have never seen this behavior.
Our next idea is to replace the entire CPCI cabinet.
Any thoughts are welcome.
Thanks,
If
- Thread starter
- #4
-
1
- #6
M
member 1453342
Guest
If you've already changed the hardware in the CPCI cabinet, then it sounds like you've changed the DSCXL's anyway, and so you've had new RAM already.
The software version you have listed is for the Assistant. What is the RMX build?
From V4 you needed 1GB DSCXL, and that meant you either increased the RAM in the older card with an extra module, and not all cards could support the extra module, or you used the newer cards with 1GB RAM installed. Are both your DSCXL cards the same hardware variant?
I suppose you are 100% sure you have not crossed an A/B cable from RTM to the LTU? The shelf can come in service when you do that, but you can get bizarre faults.
The problem with working on this is it's a big OS4K, and the testing is not without downtime. I suppose it's 24/7. But with downtime allowed, you could swap the two DSCXL's, is the problem now on CCA or CCB? If you turn off all the LTUs and unplug from RTM, do you still have the problem? Reconnect one by one, when does the problem come? There's things to try but you need downtime. APE's would help you with the IPDA downtime, if they're offline that's a different reason to CCB.
What's in the HISTA when it restarts? RTM can cause strange things too, might be worth downloading the RTM logs (act-ussu:dllogfl
In the newer 4Ks, unreachable IPDA can cause a processor switchover. If CCA talks to IPDA but CCB can't, and you switch to CCB, it will switch straight back. I think on the older DSCXLs it needed a physical layer 1 issue on the CC IPDA port to switch, not like V6 and above where it will switch on layer 3 problems.
Changing the cabinet might be useful, but it's a complete coin toss. I would spend more time trying to locate at what point the error comes. From your description it's easily reproducible.
Is anything plugged into the ATLAN? You've not got a call logger sitting on there with a 192.0.2.2 address?
Difficult to say without the HISTA. And probably difficult to say with it, by the sound of it.
The software version you have listed is for the Assistant. What is the RMX build?
From V4 you needed 1GB DSCXL, and that meant you either increased the RAM in the older card with an extra module, and not all cards could support the extra module, or you used the newer cards with 1GB RAM installed. Are both your DSCXL cards the same hardware variant?
I suppose you are 100% sure you have not crossed an A/B cable from RTM to the LTU? The shelf can come in service when you do that, but you can get bizarre faults.
The problem with working on this is it's a big OS4K, and the testing is not without downtime. I suppose it's 24/7. But with downtime allowed, you could swap the two DSCXL's, is the problem now on CCA or CCB? If you turn off all the LTUs and unplug from RTM, do you still have the problem? Reconnect one by one, when does the problem come? There's things to try but you need downtime. APE's would help you with the IPDA downtime, if they're offline that's a different reason to CCB.
What's in the HISTA when it restarts? RTM can cause strange things too, might be worth downloading the RTM logs (act-ussu:dllogfl
In the newer 4Ks, unreachable IPDA can cause a processor switchover. If CCA talks to IPDA but CCB can't, and you switch to CCB, it will switch straight back. I think on the older DSCXLs it needed a physical layer 1 issue on the CC IPDA port to switch, not like V6 and above where it will switch on layer 3 problems.
Changing the cabinet might be useful, but it's a complete coin toss. I would spend more time trying to locate at what point the error comes. From your description it's easily reproducible.
Is anything plugged into the ATLAN? You've not got a call logger sitting on there with a 192.0.2.2 address?
Difficult to say without the HISTA. And probably difficult to say with it, by the sound of it.
Arshad Iqbal
Systems Engineer
That would be a good initiative hipath4k
I think there is a need of Video channel where we all can collectively contribute.
There are no video tutorial available for Siemens products.
I have OS4K v8 and OSBiz v2 X8 available in our demo lab. let me know if that could be useful for you.
you can reach me on arshad.iqbal@gmail.com
I think there is a need of Video channel where we all can collectively contribute.
There are no video tutorial available for Siemens products.
I have OS4K v8 and OSBiz v2 X8 available in our demo lab. let me know if that could be useful for you.
you can reach me on arshad.iqbal@gmail.com
- Status