TCP/IP (trivial) issue

[TomaszSerwanski]

Hello,

Shame to ask, but did long digging in HP docs, and these do not seem to help me; got problem with IP setting on one of interfaces, story is:

----------------------------

1. there is no ip- set yet:

66-> info subnet *

TCPIP Info SUBNET \PKP.$ZB1AA.*

Name     Devicename     *IPADDRESS       TYPE     *SUBNETMASK  SuName   QIO *R

#LOOP0   \NOSYS.$NOIOP   127.0.0.0       LOOP-BACK %HFF000000           OFF N
67-> info route *

TCPIP Info ROUTE \PKP.$ZB1AA.*

Name       Subnet    Destination     Netmask         Gateway        Type Metric

#RT2       #LOOP0   127.0.0.0       255.0.0.0       127.0.0.0       H    0
68->

----------------------------

2. setting ip:

68-> add subnet #sn1, ipaddress 10.60.132.13,SUBNETMASK %HFFFFFF00, devicename L1002A, type ethernet
69-> info subnet *

TCPIP Info SUBNET \PKP.$ZB1AA.*

Name     Devicename     *IPADDRESS       TYPE     *SUBNETMASK  SuName   QIO *R

#LOOP0   \NOSYS.$NOIOP   127.0.0.0       LOOP-BACK %HFF000000           OFF N
#SN1     \PKP.L1002A     10.60.132.13    ETHERNET  %HFFFFFF00           ON  N
70-> info route *

TCPIP Info ROUTE \PKP.$ZB1AA.*

Name       Subnet    Destination     Netmask         Gateway        Type Metric

#RT8       #SN1     10.60.132.0     255.255.255.0   10.60.132.13         0
#RT2       #LOOP0   127.0.0.0       255.0.0.0       127.0.0.0       H    0
71->

----------------------------

3. unfortunately ping does not seem to work:

71-> ping 10.60.132.13 1 1
PING 10.60.132.13: 1 data bytes

----10.60.132.13 PING Statistics----
1 packets transmitted, 0 packets received, 100% packet loss
72->

----------------------------

I've tried so far several modifications of above, tried to change routes added by default, problem is that result is always same - interface remains to be 'unpingable'. Advice please, is there anything I should take care, and what is - probably - no mentioned in manuals?

Thank you in advance & regards

Tomasz

[TomaszSerwanski]

Hello,

Still trying, no luck - but there are new findings, maybe it will shed some light:

- system has both: vio and ip clim interfaces

- problems mentioned (cannot ping itself) seem to be related only to vio interfaces

- same network cable/ip address disconnected from vio, and connected to ip clim behaves as expected

So new question is - are there any know issues with cooperating between vio and ip climes? Any rules saying that, for example, systems with ip clims should not use vio ethernet interfaces?

If anyone had similar issues on systems with bot: vio and ip clims, share please.

regards

Tomasz

[TomaszSerwanski]

..so if anyone would have similar problem - seems that issue was related to missing DEFINE statement, defining correct process; as default one was used, pings had problems even if external communication worked; strange a bit, but.. :)