You got it, the plmnid was wrong so the S1 connection never came up. 

On Jul 21, 2016, at 10:10 AM, Shayne Lebrun <[email protected]> wrote:

> I believe the order is that you have to have a valid S1 connection, *then* 
> the eNodeB will try to turn on the GPS.  If the GPS works, *then* the eNodeB 
> will start turning on the antenna ports.
>  
> If you take an eNodeB out of the box, plug in a GPS, log in to the management 
> IP, and look at the timing port, the unit will never ever ever say that it 
> has timing, or even gps-comm-status.  It needs to be configured enough, and 
> cabled enough, to have a valid S1 signaling connection to the EPC.
>  
> I’ve told telrad that some UI changes, like a simple command to tell us where 
> it is in the process between ‘cold boot’ and ‘fully functional’ would be 
> nice, as well as maybe some more descriptive statuses.  ‘timing 
> gps-comm-status NoS1Server’ would be far more useful.
>  
> Or, you know, just decouple initiating the GPS device from having a valid s1 
> server.
>  
> Similarly, imagine this:
> >show ran port
> PORT  OPERATIONAL  ADMIN
> NUM   STATUS       STATE
> ------------------------------
> 1     OutOfService-NoTiming    InService
> etc
> Or:
> >show ran port
> PORT  OPERATIONAL  ADMIN
> NUM   STATUS       STATE
> ------------------------------
> 1    OutOfService-NoS1    InService
>  
> Or maybe even:
> >show ran port
> PORT  OPERATIONAL  ADMIN  ERROR
> NUM   STATUS       STATE             STATE
> -----------------------------------------------
> 1     OutOfService    InService     NoTiming or NoS1
>  
>  
> Or maybe couple it into show status device:
> >show status device
> general {
>     product-type     COMPACT;
>     product-subtype  ENB;
>     compact-model-type BreezeCompact3000;
> }
> inventory {
>     hw-ver           "1 (CORE: E500MC v3.2)";
>     serial-number    95018308;
>     main-sw-ver      0606.04013;
>     backup-sw-ver    0600.02616;
>     running-sw       MainSW;
>     boot-ver         2013.01.00014;
>     up-time          2016-07-21T11:07:27-05:00;
> }
> Service-prerequisites{
>   S1-signalling    VALID;
>   Timing               VALID;
>   Ran-ports         VALID;
> }
>  
> Or something like that.
>  
>  
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> David Peterson
> Sent: Thursday, July 21, 2016 11:45 AM
> To: [email protected]
> Subject: Re: [Telrad] GPS
>  
> It will also look like that if your S1 is down.
>  
> David
>  
>  
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> Steve Discher
> Sent: Thursday, July 21, 2016 11:39 AM
> To: Scott Lambert <[email protected]>
> Subject: Re: [Telrad] GPS
>  
> Did you follow the wiring diagram that came with the GPS to make the cable?  
> If so, they are fried.  They require a standard Cat5 cable, not the one on 
> the diagram that seems to still be included with some antennas.  That wiring 
> diagram was for a different radio platform, not the Compact and we have had 
> many operators follow it and kill their GPS.  Telrad has been RMA ing any 
> that happened to.  We went through our tock and removed those directions but 
> I suspect there are some floating around still.
>  
>  
> On Jul 21, 2016, at 9:21 AM, Dan Petermann <[email protected]> wrote:
>  
> We are putting up 2 new sectors and both of them have no GPS comms. 
>  
> Any idea of what to look for? I have a hard time believing that both GPS 
> antennas are bad.
>  
>  
> BreezeCompact> show timing
> timing gps-comm-status Down
> timing external-1pps-status NotExist
> timing coordinates longitude ""
> timing coordinates latitude ""
> timing coordinates altitude 0
> [ok][1969-12-31 17:02:24]
> _______________________________________________
> Telrad mailing list
> [email protected]
> http://lists.wispa.org/mailman/listinfo/telrad
>  
> Steve Discher
> [email protected]
> ISP Supplies Office: (855) 947-7776 / Fax: (866) 585-2175 
> 10770 State Hwy. 30, Suite 200 College Station, TX 77845
> http://www.ispsupplies.com
> Follow my WISP Blog
> Follow the WirelessRoadshow.net
>  
>  
> <image001.jpg><image002.jpg> <image001.jpg><image002.jpg> 
> <image001.jpg><image002.jpg> <image001.jpg><image002.jpg> 
> <image001.jpg><image002.jpg>
>  
> _______________________________________________
> Telrad mailing list
> [email protected]
> http://lists.wispa.org/mailman/listinfo/telrad

_______________________________________________
Telrad mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/telrad

Reply via email to