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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reseating IPSI Board

Status
Not open for further replies.

noside12000

Technical User
Jan 23, 2012
19
US
Hello,

We have an issue wherein a remotely managed EPN has gone down but the IPSI A and B are both pingable and was said active by our network team.

I've tried administering it by doing busy/reset/release but it says "board not inserted".

I'm planning to have the IPSI boards reseated but can someone give me any advise on what to look out for that activity?

Is the activity the same sa reseating a DS1 or Medpro?

Appreciate the response. Thank you.


 
Look at the log files in /var/log/ecs. It's probably unstable network connectivity. If that much isn't in place, you can't make CM busy them or anything.
 
Before attempting to reseat the board manually, you can log into the IPSI remotely (if it is actaully on the network) to validate the parameters and see if the servers are listed. You can also reset the IPSI board from the CLI. Look in the Server Commands Maintenance Manual for how to use the ipsisession command to enable ssh login from the CM command line.

You might also want to look at the logs to see what kind of issues the PN is having.

Lastly you might want to validate your IPSI software is up to date.
 
Check the logs that kyle mentioned. Grep for sanity and see if you are failing any. If they are failing I would go back to the network team and ask them to verify some stuff (depending on what the ECS log said).

 
Thank you so much for the reply guys. I did try to have it re-seated no good. What I did try was to use the command "get forced-takeover ipserver-interface port-network 18x" and after that it worked. What wonders me is that, the ESS doesn't reflect the said IPSI registering on its end and that is also why I wasn't doing that command in the first place.


 
You failed to mention that you had ESS servers
Command: status ess clusters
Command: status ess port-networks

Your ESS server should have alarmed with LIC-ERR and SP-REG-S and ESS
Your Main server should have alarmed with SP-REG-M and EXP-PN PN 18 and PKT-INT 18A

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top