Adding a bogus route to simulate network outage

[Joel Aquino_2]

Trying to simulate a network outage to exercise my HP NNM software running on HP-UX 11.31 ia64 system.

I added a bogus route for a destination IP, yet I can still ping the destination IP.

Used the command "route add host DEST-IP GW 1"

The gateway IP that I used is not pingable.

Any ideas?

[Matti_Kurkela]

Perhaps the Dead Gateway Detection feature of HP-UX disabled your bogus route.

Run:
ndd -get /dev/ip ip_ire_gw_probe

If it responds "1", Dead Gateway Detection is enabled. To disable it, run:

ndd -set /dev/ip ip_ire_gw_probe 0

Then remove and re-add your bogus route.

MK

[Joel Aquino_2]

I ran ndd -get /dev/ip ip_ire_gw_probe but it returned "0"

[John Dvorchak]

that real destination wouldn't happen to be on the same subnet would it?

[Joel Aquino_2]

No, the real destination I am trying to prevent communications with is on a different subnet.

With the route add command, it seems I am required to enter a gateway address that is on the same subnet as my HP-UX server.

[Steven E. Protter]

Shalom,

If its a test system, how about actually having a network outage.

Pull the cable or have the network admin misconfigure the port.

Make sure you still have console access and you will really see what happens.

Breaking the software network configuration is not imo realistic. Its a stupid human trick that is not how networks get broke. They get broke by the methods mentioned in paragraph two of this port.

SEP

[Joel Aquino_2]

Hi Steven, our NNMi server is monitoring production networked sites. Even creating ACLs on the router/switches to block just my NNM server's IP would temporarily cause a loss of communication for the whole site.

While it may not be a real-world scenario, it is better than disrupting critical business services.

Thx

[Joel Aquino_2]

How about this question instead...In HP-UX 11.31, is there a way to configure my system so that it is not able to communicate with another subnet/IP address yet still allow it to communicate with all others?

This HP system is hosted on an HP VM and the network team is not comfortable creating an ACL affecting the trunked network link that is shared among other VMs on this host.