Comtech EF Data MIDAS 4 Software Installation User Manual
Page 35
MIDAS 4 Software Installation Guide, Rev.4
System Preparation
2–15
Testing and Verification
Step
Procedure
Troubleshooting
1
From the Controller Server, PING
the NMS Server. Verify 100% re-
sponse with average delay of
< 30 msec.
A failed PING attempt between the
Controller Server and the NMS Server
shall not occur if they are on the same
physical sub-network unless serious
NIC problems exist (hardware or
driver).
2
Attempt to PING to and from the
Controller Server from any other
device in the network and verify no
response.
If any other network device can PING
the Controller Server, verify IP Ad-
dress and Subnet Mask settings.
3
From the NMS Server, PING the
Controller Server. Verify 100%
response with average delay of
< 30 msec.
A failed PING attempt between the
Controller Server and the NMS Server
shall not occur if they are on the same
physical sub-network unless serious
NIC problems exist (hardware or
driver).
4
Attempt to PING to and from the
NMS Server from any other device
in the network and verify no re-
sponse.
If any other network device can PING
the NMS Server, verify IP Address and
Subnet Mask settings.
N
N
M
M
S
S
S
S
e
e
r
r
v
v
e
e
r
r
–
–
R
R
e
e
m
m
o
o
t
t
e
e
N
N
M
M
S
S
W
W
o
o
r
r
k
k
s
s
t
t
a
a
t
t
i
i
o
o
n
n
(
(
O
O
p
p
t
t
i
i
o
o
n
n
a
a
l
l
)
)
The network changes to prepare for the installation of MIDAS 4 comprise
routing and filtering settings. The MIDAS NMS Server and each MIDAS
Remote NMS Workstation require a high speed (>2 Mb/s), low latency con-
nection. This connection(s) shall be isolated to only allow traffic between the
NMS Server and each individual Remote NMS Workstation.
This can be accomplished several ways.
• A connection using a 10/100 BaseT hub.
• A connection using a 10/100 BaseT Layer 2 Switch or Router.