Karlnet
[Top] [All Lists]

RE: [Karlnet] RE: MIB strings from Demarc PRISM 2.5 cards

To: <karlnet@WISPNotes.com>
Subject: RE: [Karlnet] RE: MIB strings from Demarc PRISM 2.5 cards
From: "Demarc \(tony\) 908-996-7995" <tonylist@wwwbiz.com>
Reply-to: karlnet@WISPNotes.com
Date: Sun, 11 Aug 2002 22:17:18 -0400
List-post: <mailto:karlnet@WISPNotes.com>
Norm

Please keep us updated on the progress!

Sincerely
Tony Morella
Demarc Technology Group
Office: 908-996-7995
Cell: 908-246-9170
Fax: 908-847-0202
email: tony@demarctech.com
http://www.demarctech.com
Wireless Solution Provider


-----Original Message-----
From: karlnet-admin@WISPNotes.com [mailto:karlnet-admin@WISPNotes.com]
On Behalf Of Norm Young
Sent: Sunday, August 11, 2002 7:46 PM
To: karlnet@WISPNotes.com
Subject: Re: [Karlnet] RE: MIB strings from Demarc PRISM 2.5 cards


That's a good point.  The 180mW card is on the other side of the PtP
link, so it's not slotted in the AP-1000. I'll reflash the "problem
child" with the new firmware and see what happens then.  Thanks Tony.

Norm

----- Original Message -----
From: "Demarc (tony) 908-996-7995" <tonylist@wwwbiz.com>
To: "'Norm Young'" <npyoung@applegatebroadband.net>;
<karlnet@WISPNotes.com>
Sent: Sunday, August 11, 2002 4:26 PM
Subject: [Karlnet] RE: MIB strings from Demarc PRISM 2.5 cards


> Norm
>
> FYI You have two 100mW cards and one 180mW card. The 180mW card does 
> draw 20mA more then the 100mW. This should not be causing a problem 
> but as you know the AP-1000 is picky about power.  Also there is a new

> firmware that might help on the website.
>
> Sincerely
> Tony Morella
> Demarc Technology Group
> Office: 908-996-7995
> Cell: 908-246-9170
> Fax: 908-847-0202
> email: tony@demarctech.com
> http://www.demarctech.com
> Wireless Solution Provider
>
>
> -----Original Message-----
> From: Norm Young [mailto:npyoung@applegatebroadband.net]
> Sent: Sunday, August 11, 2002 6:51 PM
> To: karlnet@WISPNotes.com
> Cc: tony@demarctech.com
> Subject: MIB strings from Demarc PRISM 2.5 cards
>
>
> I'm having a problem with hang on reboot on my AP-1000 running KN 4.02

> with two of Tony's 100mW PRISM 2.5 card in it.  The hang was in the 
> last light, or the .11/3 or "B" interface. It has been running very 
> smoothly for the last month with these same cards in it, but the 
> problem is eluding an easy answer.  The only change was that 5 days 
> ago, the .11/3 or "B" interface, which is being used as a backhaul, 
> recently got a 100mW PRISM card on the other side of the link.  
> Interestingly enough, the signal levels reported back were different 
> by 5 dB, even though the antennas and radios were
> indentical on both sides.   I swapped the two radio cards in the the
> AP-1000, and walla! signal levels in the backhaul went to indentical 
> (-75dB), as it should be.  So, something strange about the .11/3 
> radio.
>
> In probing around a bit with a MIB browser in the AP-1000, I noticed 
> that the strings that came back from the two, visually identical cards

> slotted in the AP-1000 revealed some differences.
>
> .11/3 was "IEEE 802.11 Wireless LAN/PC Car IEEE 802.11 Wireless LAN/PC

> Car STA Var=6 Ver=1.03; 4;"
>
> but that from .11/2 was:
>
> "IEEE 802.11 Wireless LAN/PC Car STA Var=6 Ver=1.03; 4;"
>
> Seems that the /3 card has some scrambled info in it's description.
>
> Note that the id string from the other side of the backhaul, which is 
> a visually identical 100mW PRISM 2.5 card is: "IEEE 802.11 Wireless 
> LAN/PC Car STA Var=6 Ver=1.03; 4;"
>
> Which seems to match that of the, what is beginning to look like, 
> known good, radio in the AP-1000.
>
> Any possiblity that this could be the source of the hanging?  Will 
> reflashing the /3 radio card take care of this situation?
>
> Norm
>
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com 
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>
>

_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet


<Prev in Thread] Current Thread [Next in Thread>