fix vty tests: long timeout due to unreachable STP address
The doc/examples/osmo-msc SCCP config examples with 10.23.42.1 as asp ip-remote cause >5 minutes timeout for each VTY config test being run before the VTY becomes available. This hugely elongates the config tests, we didn't spot it before because it does succeed after that timeout. Rather use link-local addresses in order to immediately note the lack of connection and carry on with the VTY config tests. Related: OS#2333 Change-Id: I5ea4ef8a7e181bd3a38edf9c3b5d098f6ba65ee5
This commit is contained in:
parent
834f94a2cb
commit
ca4875f133
|
@ -18,7 +18,7 @@ cs7 instance 0
|
|||
point-code 0.23.1
|
||||
asp asp-clnt-OsmoMSC-A-Iu 2905 0 m3ua
|
||||
! where to reach the STP:
|
||||
remote-ip 10.23.24.1
|
||||
remote-ip 127.0.0.5
|
||||
! local-ip 10.23.24.1
|
||||
msc
|
||||
cs7-instance-a 0
|
||||
|
|
|
@ -17,11 +17,11 @@ network
|
|||
cs7 instance 0
|
||||
point-code 0.23.1
|
||||
asp asp-clnt-OsmoMSC-A 2905 0 m3ua
|
||||
remote-ip 10.23.24.1
|
||||
remote-ip 127.0.0.5
|
||||
cs7 instance 1
|
||||
point-code 0.23.2
|
||||
asp asp-clnt-OsmoMSC-Iu 2905 0 m3ua
|
||||
remote-ip 10.23.24.2
|
||||
remote-ip 127.0.0.6
|
||||
msc
|
||||
cs7-instance-a 0
|
||||
cs7-instance-iu 1
|
||||
|
|
Loading…
Reference in New Issue