IPSI State of Health - What's wrong with my IPSI?

[Midstream]

IPSI number 2 is ne to the system and has never registered. What's wrong with this thing, please?

list ipserver-interface

IP SERVER INTERFACE INFORMATION

Port Pri/ Primary/ Primary/ Primary/ State Of
Ntwk Sec Secondary Secondary Secondary Serv Control Health
Num Bd Loc IP Address Host Name DHCP ID State State C P E G
---- ------ --------------- ---------------- --------- ----- ------- -------
1 1A01 10.30.15.19 10.30.15.19 ipsi-A01a IN actv-aa 0.0.0.0

2 2A01 10.40.15.20 10.40.15.20 ipsi-A02a OUT active 0.1.1.0



That last column is trying to tell me something and I don't know where to look it up. Can anyone point me to the right manual please?

 

[simreal]

According to the documentation ... 0.1.1.0 means "".


I would session into the IPSI, verify there is a gateway administered if it needs one and make sure the IP and subnet are administered. Also check the speed/duplex. In out invironment we lock everything to 100FULL.


From Sat enter "go shell"

From shell your commands are:
"ipsisession -d -c 01a" (or whatever IPSI you want) - this disables any previous session admin.

"ipsisession -c 01a" (or whichever IPSI you want) - this enables the session, copy the password given.

"ssh init@ipsi-a01a" (replace the IPSI number as needed) -type "yes" when prompted, paste in password, hit enter.

select option 1 for Admin.

type "ipsilogin" with the following login info (craft / serv1ces)

hit enter

Now your at the IPSI command prompt. You can type "help" at any time for a list of commands. The commands you'll need are:

show control interface
show port 1
show qos

The process should look something like this:

ssh service disabled.
mhidalgo@TPvoiceserver02> ipsisession -c 08a
ssh service enabled.
Use this password for the ssh session: Fq0PlC8q
mhidalgo@TPvoiceserver02> ssh init@ipsi-a08a
The authenticity of host 'ipsi-a08a (x.x.x.x)' can't be established.
DSA key fingerprint is 61:d9:f1:90:f2:59:c1:69:4a:55:23:c9:00:23:13:1d.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/var/home/defty/.ssh/known_ho
sts).
init@ipsi-a08a's password:


IPSI SSH Options:
-------------------------------
Enter '1' for IP Administration
Enter '2' for VxWorks Shell

1

TN2312 IPSI IP Admin Utility
Copyright Avaya Inc, 2003, All Rights Reserved

[IPSI]: ipsilogin

Login: craft
Password:


[IPADMIN]: show control interface

Control Network IP Address = x.x.x.x
Control Network Subnetmask = 255.255.255.0
Control Network Default Gateway = x.x.x.1
IPSI is not configured for DHCP IP address administration

[IPADMIN]: show port 1
Link: established
Autonegotiation: enabled
Speed: 100 Mb
Duplex: half
Flow control: disabled

[IPADMIN]: show qos

QoS values currently in use:
VLAN tagging : on
VLAN id : 0
VLAN user priority : 3
Diffserv value : 26

QoS values to be used after next reset:
VLAN tagging : on
VLAN id : 0
VLAN user priority : 3
Diffserv value : 26

 

[simreal]

Sorry, I forgot to paste the documentation statement.

The documentation says "The pattern 0.1.1.0 usually means there is a wrong cabinet type administered
a connectivity problem, such as an improperly terminated cable."

http://support.avaya.com/elmodocs2/comm_mgr/r3/pdfs/03_300432_1.pdf

 

[mikeydidit]

http://support.avaya.com/elmodocs2/comm_mgr/r3_1/pdfs/maintenance/03_300430_2_1.pdf

page 1432 should give you what you need rockspop.

Let me know if you need more on this.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[Midstream]

SUPER! Just super!

I'll bet that I've got a TDM terminator misapplied. I'll check that connectivity when I can get a pair of eyes on site and report back to close this issue.

 

[Midstream]

Allright, here's the deal. This thing's in London and I'm in Minneapolis.

There was a bad CLAN card shorting out the bus.


We replaced all the TDM adapters, erased the translations on the IPSI and then reloaded the translations as outlined in document KB01006520. Even tried to replace it with a new IPSI. There was no joy in Mudville until the tech started rebuilding the cabinet piece by piece and noticed when the CLAN was inserted the TDM bus shorted out and the cabinet lost connectivity.

New CLAN, no more problems!

Chalk one up for Martin and Mrjedi in London!