M and MSM Series
1751693 Members
5076 Online
108781 Solutions
New Discussion

MSM760 strange errors...

 
SOLVED
Go to solution
Niko-Lizard
Advisor

MSM760 strange errors...

Hi There.

 

On my MSM760 Team I am experience some errors. Can anyone explain them to me?
I have tried googling it, but cannot find an answer.

 

First error:
store-devices: SG24XXXXXX Couldn’t identify device 169.254.0.5
I can ping the address from the controllers web interface. However, I cannot find it any ware in our switch environment or in MSM ARP table or log files. How can I track the device? It shows every 5-10 seconds I log.

 

Second error:
webredirect: assert: ../webs.c websParseFirst 908 (text && *text).
This error do not give me anything…

 

Kind regards

5 REPLIES 5
JesseR
Regular Advisor

Re: MSM760 strange errors...

First error... the SG24xxxxxx looks like a serial # for an MSM AP to me? 169.254 is not a valid useable IP address, that's what devices get when they aren't given a proper address from a DHCP server.

No idea on the second error.
Jesse R
Source One Technology, Inc.
HP Partner


MSM 5.7.x deployment guide:

Niko-Lizard
Advisor

Re: MSM760 strange errors...

Hi There.

 

The SG24# is the seriel number of one of the controllers.

 

 

/Niko-Lizard

SBA_Mark
Occasional Visitor

Re: MSM760 strange errors...

Aren't 169.x.x.x link-local addresses issued by the APs for tunnels they create back to the controller?

MSMenthousiast
Frequent Advisor

Re: MSM760 strange errors...

Hi

For this: store-devices: SG24XXXXXX Couldn’t identify device 169.254.0.5

Are you seeing this repeatedly? That could have appeared because your AP lost connectivity/rebooted. I dont think you should worry unless it appears all the time.

For this:
webredirect: assert: ../webs.c websParseFirst 908 (text && *text).

Were you using the WEBUI at that moment? Was a client on an HTML-based login VSC? Custom web-pages?

thanks
Arimo
Respected Contributor
Solution

Re: MSM760 strange errors...

The management traffic between the controller and APs is done via a tunnel, and within that tunnel they use 169.254 -addresses. So these addresses will never show up in your LAN.

 

I've not seen the "couldn't identify" -message before, but when it's associated wiht store-devices and an AP tunnel IP address it seems quite clear - the controller can't recognize this AP for one reason or another.

 

Webredirect refers to HTML login on VSC. It's not related to the controller GUI, so if you're not using HTML login for VSC it shouldn't affect your wireless. However assert is worrying. If you haven't done so already, please contact your local support center.

 

To help us get started please gather from the controller the config, filtered and unfiltered logs and sysinfo file for support.


HTH,

Arimo
HPE Networking Engineer