07/15/2015
3
b.
Launch an SSH session to site device and execute the
show snmp summary
command:
i.
Host addresses:
Tower East 01 -
172.20.6.14
Tower East 02 -
172.20.6.30
Tower Central 01 -
172.20.6.50
Tower Central 02 -
172.20.6.31
Tower Mountain -
172.20.6.51
Tower Pacific -
172.20.6.52
DAS –
172.20.6.17
ii.
Community strings
readwrite – administrator
readonly – public
c.
ping
the appropriate host address to confirm the site device can communicate with
Optima
d.
Verify the Restore point by right clicking on the site’s Remote NE, selecting
View NE
Details
and checking the
Software Restore Points
tab for a valid restore point
(designated by a green status indicator for the most recent restore point)
e.
Check Optima to see if the events in question have cleared
Site not accessible
Follow these steps for
Element is Down
events:
Initial Triage:
1.
Using the DOS Command Prompt, send a constant ping to the RMM/RMC for at least 15
minutes (use Ctrl-C to stop)
a.
ping -t
10.4X.XXX.XXX
b.
If the ping response is
Request Timed Out
,
this indicates that the network knows how
to route the IP traffic destined for this IP address (i.e. the ping to the RMM/RMC), but
the device is not responding
i.
This may be due to a loss of power to the RMM/RMC or a loss of network
connectivity for
LESS than 18 hours
c.
If the ping response is
TTL Expired in Transit
, this indicates that the network does not
know how to route this traffic, causing the ping packet (ICMP packet) to go into a
routing loop for 30 hops and then returns this response
i.
This may be due to a loss of power to the RMM/RMC or a loss of network
connectivity for
MORE than 18 hours
d.
Use the
tracert
10.4X.XXX.XXX
to check network routing to the remote site
i.
If no route contact network engineering group to validate findings and assist
further before dispatching to site
