app.log message - rtosSocketSetOptions

[Anonymous]

We recently deployed a mix of VVX 300 and 400 phones to a location and setup an FTP server for provisioning and DHCP scope options for phones to automaticlally login and grab updates automatically and save log files. 

We started noticing two different phones leaving recurring errors in their respective logs.  Does anyone know what they mean and what the appropriate procedure is to address them so they don't report them anymore?  I also noticed that some phones are leaving <mac-address>-<software-version>-core.620.tar.gz, <>-<>-core.591.tar.gz, and other 3-digit core files on the FTP server now (for example, 0004f280d9dc-5.0.1.4068-core.620.tar.gz).  Is this the phone backing itself up?

app.log 1

1212092046|rtos |4|00|rtosSocketSetOptions - Can't set VLAN qos with user_priority (5) failed with (error no = 0xffffffff)
1212092046|rtos |4|00|rtosSocketSetOptions - Can't set VLAN qos with user_priority (5) failed with (error no = 0xffffffff)
1212113730|rtos |4|00|rtosSocketSetOptions - Can't set VLAN qos with user_priority (5) failed with (error no = 0xffffffff)
1212113730|rtos |4|00|rtosSocketSetOptions - Can't set VLAN qos with user_priority (5) failed with (error no = 0xffffffff)

app.log 2

000034.028|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 49 is out of range
000034.028|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 50 is out of range
000034.028|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 51 is out of range
<-truncated for sake of brevity->

1212113130|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 261 is out of range
1212113130|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 262 is out of range
1212113130|cfg  |5|00|Prm|Array parameter attendant.resourceList.x.address index 263 is out of range

Thank you

[SteffenBaierUK]

Hello jplarsonqg,

welcome to the Polycom Community.

The MAC address you posted is associated with a Polycom account so the correct escalation method would be to work with the SE or Polycom employee who has provided that VVX410.

In addition a core upload is a major cause of concern as this only happens when the VVX reboots due an issue.

I believe, based on the core filename you are running UCS 5.0.1 on either LYNC or a Broadsoft Platform.

In order to analyze this we would need the current configuration and the call scenario this is appearing and as this is ousode of the scope of the community please follow this up as advised above.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services