Commit 7f8706e9 authored by Shashi Guruprasad's avatar Shashi Guruprasad

For sim hosts, we need to wait till the simulation has started before

sending an ISUP. ISUP is now sent as the first event from the nse scheduler.
parent 15083d37
......@@ -7,7 +7,9 @@
#
global CLIENTVARDIR
global CLIENTBINDIR
set CLIENTVARDIR @CLIENT_VARDIR@
set CLIENTBINDIR @CLIENT_BINDIR@
# consults tmcc hostnames database to translate hostname to IP
# returns ip address of name
......@@ -481,4 +483,13 @@ if { [info exists tbroutes] } {
unset tbroutes
}
# Adding an event to send an ISUP event to the testbed
# Note that the actual events specified by the user will
# come from the event system after a little while. So, this
# first event at 0.0 will ensure that the simulator scheduler
# has subscribed to the event system and is processing the
# first event
$ns at 0.0 {exec echo "Informing the testbed that we're up and running ..." > /dev/console}
$ns at 0.0 "exec $CLIENTBINDIR/tmcc state ISUP"
$ns run
......@@ -124,11 +124,14 @@ fi
if [ -x $BOOTDIR/rc.simulator ]; then
echo "Starting Network Simulation ..."
$BOOTDIR/rc.simulator
# The simulator will send the ISUP once it is
# up and running
echo "Will Inform the testbed that we're up and running after simulator initialization ..."
else
echo "Informing the testbed that we're up and running ..."
$BINDIR/tmcc state ISUP
fi
echo "Informing the testbed that we're up and running ..."
$BINDIR/tmcc state ISUP
# Now boot vnodes. Doing it after ISUP is better; os_setup will consider
# the node ready, and move onto waiting for vnodes to boot.
if [ -x $BINDIR/bootvnodes ]; then
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment