Testing your backup ISDN network

Unanswered Question
Jul 30th, 2007
User Badges:

Wondering how everyone else tests their ISDN redundant network? Does anyone automate or schedule tests of your Redundant network to make sure all routes will route probably in case of a primary link failure? How often do you test? And can you do this without affecting your production network?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
paolo bevilacqua Mon, 07/30/2007 - 10:40
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Good question.

It think it can be split in two parts:

1. ISDN connectivity. A proper designed network will allow pings to bring up ISDN and then links will go down by inactivity. This should be simple to schedule via script. I would do this bi-weekly, for example, and can be done in normal working hours.

2. overall routing while in backup situations. if .1. succeeds, you may want test this as well. Probably the easiest way is to shutdown some strategically chosen interfaces and see if network reconverges. A script to do this and test results is much more complicated, but doable. for safety, I would do this like monthly, and outside working hours.

Hope this helps, please rate post if it does!

fargier Mon, 07/30/2007 - 23:19
User Badges:


I test the isdn one time per month. Route was checking first time I make the configuration.

If the configuration don't change, don't sure it necessary to test the route.

But one time per month I check the isdn line with :

isdn test call interface bri 0/2/0 012345678910

where 012345678910 is the phone number of the remote site.

This test is in an unix script and i received a mail if it's working fine.

Testing the isdn with command isdn test don't affect production.


This Discussion