HP X.25/9000 User's Guide HP-UX 11i v3 (5900-1523, August 2011)

If no IP communication is possible (ping to a local IP address fails) and netstat -a shows no
entries despite the fact that x25init reported a successful IP mapping, the likely cause is:
• the device=x25_card_device parameter has not been added to the /etc/x25/
ip_to_x121_map file. See the section, “IP-to-X.121 address mapping table” (page 138) in
this chapter.
You can also use the netstat command with the -r option to get information about IP addresses
associated with a particular interface.
Note 5-3 – Exit
Your local IP over X.25 configuration is correct. You can use ping to verify connections if the
remote host:
• is operational
• has X.25 initialized
• is compatible with IP and ICMP protocols
• and has an entry for your node in its map table (can map your IP address to your X.121
address)
If you still experience problems, ask the remote host System Administrator to check the IP over X.25
configuration on the remote side of the connection.
Figure 32 Flowchart 5 – IP over X.25 check
Recovering from a power failure
For systems with a backup power supply
If your site is equipped with a backup power supply, system memory will be preserved in the event
of power failure. However, because your X.25 hardware does not have backup capability, any
on-board RAM-based memory is lost.
Recovery from a power failure is automatic when the /etc/powerfail script is invoked by
/etc/inittab. Otherwise SMH (or x25init) must be used to manually re-initialize the interface
after a power failure.
The recovery mechanism informs the X.25 driver of the power failure. The X.25 driver then “marks”
the interface as “down” and a DISCONNECT INDICATE is received on all open SVCs.
For systems with no backup power supply
If your system does not possess the battery backup option, both system memory and interface card
memory are lost. You must reboot your system.
Recovering from a power failure 135