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!

S8400

Status
Not open for further replies.

hdbeavis

Technical User
Oct 12, 2006
56
I have an S8400 with TN8412AP SIPI Board. I can get all the way through the wizard and get the SIPI configured. When I go into CM I change my dadmin password and do my save trans and reset sys 4. After that I do my change sys IPserver and enable my IPSI control. The next thing I try to do is "add ipserver 1." When I go in and add the IP address of my SIPI and hit enter it says it was successful. But.....I immediately get alarms in CM. I get an "EXT-PN" and "PKT-INT" When I do a lis con all it doesn't see anything. It shows tone clock and says no board. I have reloaded CM and went through the hole speel again and got the same result at the same point. FYI......I have given the SIPI and the ETH A a seperate IP address than the Corporate LAN. I have rebooted and rebooted and rebooted to no avail.....Can anyone help?? P.S. I am supposed to cut tonight!!!!!I have pushed it back to tomorrow night.(I have a SIPI and S8400 on the way)
 
Can you PING the SIPSI from the S8400? Are you using the cross over stub cable provided with the kit?
 
Yes I can ping from the SIPI to the 8400. In the web interface I can ping the SIPI from the 8400 also. Yes I am using the short blue cross over cable they provided.
 
Well Avaya wasn't much help. There answer was it was a bad SIPI, I had already replaced it once and had the same problem. Here is what I did...reseat the card and as soon as you put it in hold the little reset button on face of card until it says "Aoo", it will be flashing. Immediately pull card out and reseat card again. I then reconfigured my SIPI and it worked. Doing this returns the SIPI to "Factory default". The only thing I can think of is that the first time I configured the SIPI something got corrupted and "Confused" the card, Avaya tech thinks something may have been wrong with it to begin with. They get alot of calls on this and usually just chock it up to being a bad card. He has personally experienced BP's who had received multiple bad cards on one install. He was going to document this procedure and distribute it to the other Avaya Techs, as a possible solution. Avaya could not find any documentation on this procedure but my third tier 3 tech that day was patient enough to work with me trying a few things and we came up with this. We actually had another business partner call a few weeks later with this same problem and this worked for him....good luck. Did you ever get your board up?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top