🚀 go-pugleaf

I spoke with Sean Kennedy and he reported the following.  Apparantly 
Nearnet has backup T1 and T3 connectivity through the peer 192.52.71.8.
Sean explained that Nearnet had their traffic split so that half went
to Princeton and half went to Pittsburgh.  It was split so that
interface 192.52.71.8 handled the traffic to Princeton and 192.52.71.7
handled the traffic to Pittsburgh.  Now the deal is that 192.52.71.8
is currently unreachable.  I cannot find it.  It is not in our hostfile.
The only reference I have to it is the following line in the conf file
on rcp-19-1.

egpneighbor     192.52.71.6     nogendefault egpmetricout 128 
intf 192.52.71.8 ASin 281 validate.

A dns lookup reveals that 192.52.71.7 and 192.52.71.8 have the same
hostname, nss-bbn.near.net.  If you telnet to it, you reach psp-19-10.
192.52.71.7 is the address for the ethernet interface on psp-19-10.
Now my question is, where is 192.52.71.8?

stevep