SoundPoint 321 Vlan Weirdness

[Anonymous]

BACKGROUND INFO:

Phone: SoundPoint 321

UCS Ver: 4.0.11

Native Vlan: 1 (192.168.0.0/24) ifname=eth2

Voice Vlan: 5 (192.168.5.0/24) ifname=eth2.5

isc DHCP server on both subnets

option 128 defined as VLAN-A=5; per UCS Admin guide

LLDP and CDP are DISABLED

ISSUE:

Upon reboot, the phone performs a DHCPDISCOVER via if eth2 and is assigned an address on Vlan 1 (192.168.0.88) and receives a valid DVD string (VLAN-A=5) via option 128. The phone correctly sets the vlan id to 5. It then releases the Vlan 1 address and performs a DHCPDISCOVER via if eth2.5. For some unknown reason it simultaniously perrforms a DHCPDISCOVER via if eth2 (again). The phone recieve DHCPOFFERS from the DHCP server on both subnets within seconds of each other although the offer from the Vlan1 subnet occurs before that from Vlan5. Some weirdness follows in which it appears that the phone attempts a DHCPREQUEST for 192.168.0.88 on the 192.168.5.0 subnet which, of course, the server denies (DHCPNAK). At that point it appears that the phone rolls back to Vlan1 and requests and receives a lease for 192.168.0.88.

QUESTION:

What is wrong with this phone?

RELEVANT LOG SNIPS, ETC:

DHCP LOG LINES:

Dec 19 23:30:07 masada dhcpd: DHCPDISCOVER from 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:08 masada dhcpd: DHCPOFFER on 192.168.0.88 to 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:09 masada dhcpd: DHCPREQUEST for 192.168.0.88 (192.168.0.247) from 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:09 masada dhcpd: DHCPACK on 192.168.0.88 to 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:10 masada dhcpd: DHCPRELEASE of 192.168.0.88 from 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2 (found)
Dec 19 23:30:14 masada dhcpd: DHCPDISCOVER from 00:04:f2:a6:7b:0c via eth2.5
Dec 19 23:30:14 masada dhcpd: DHCPDISCOVER from 00:04:f2:a6:7b:0c via eth2
Dec 19 23:30:14 masada dhcpd: DHCPOFFER on 192.168.0.88 to 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:15 masada dhcpd: DHCPOFFER on 192.168.5.51 to 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2.5
Dec 19 23:30:15 masada dhcpd: DHCPREQUEST for 192.168.0.88 (192.168.0.247) from 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2.5: wrong network.
Dec 19 23:30:15 masada dhcpd: DHCPNAK on 192.168.0.88 to 00:04:f2:a6:7b:0c via eth2.5
Dec 19 23:30:15 masada dhcpd: DHCPREQUEST for 192.168.0.88 (192.168.0.247) from 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2
Dec 19 23:30:15 masada dhcpd: DHCPACK on 192.168.0.88 to 00:04:f2:a6:7b:0c (Polycom_0004f2a67b0c) via eth2

TCPDUMP ON IF eth2.5 (Vlan5):

root@masada:/etc/dhcp tcpdump -vvvv -i eth2.5 ether host 00:04:f2:a6:7b:0c
tcpdump: listening on eth2.5, link-type EN10MB (Ethernet), capture size 65535 bytes
23:30:14.110492 IP (tos 0x0, ttl 32, id 56697, offset 0, flags [DF], proto UDP (17), length 555)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:04:f2:a6:7b:0c (oui Unknown), length 527, xid 0x9249903d, Flags [none] (0x0000)
          Client-Ethernet-Address 00:04:f2:a6:7b:0c (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            MSZ Option 57, length 2: 1492
            Parameter-Request Option 55, length 11:
              Subnet-Mask, BR, Option 160, TFTP
              Default-Gateway, Time-Server, NTP, Time-Zone
              Domain-Name-Server, Domain-Name, LOG
            Hostname Option 12, length 20: "Polycom_0004f2a67b0c"
            Vendor-Class Option 60, length 120: "^@^@6=s^A^GPolycom^B^USoundPointIP-SPIP_321^C^P2345-12360-001,1^D^_SIP/4.0.11.0583/21-Jun-16 17:15^E^^UP/5.0.11.0282/08-Jun-16 19:39"
            T125 Option 125, length 120: 13885,1929447248,1869379939,1869414933,1399813486,1682993001,1853114704,760434761,1348416306,822284338,859059501,825373494,808267824,824979716,525551952,791948848,774975790,808794163,791818541,1249209901,825630769,926560565,85874000,792014384,774975790,808597554,791689261,1249209901,825630769,960115513
            END Option 255, length 0
23:30:15.111297 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 329)
    192.168.5.254.bootps > 192.168.5.51.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 301, xid 0x9249903d, Flags [none] (0x0000)
          Your-IP 192.168.5.51
          Server-IP 192.168.5.254
          Client-Ethernet-Address 00:04:f2:a6:7b:0c (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Offer
            Server-ID Option 54, length 4: 192.168.5.254
            Lease-Time Option 51, length 4: 86400
            Subnet-Mask Option 1, length 4: 255.255.255.0
            BR Option 28, length 4: 192.168.5.254
            TFTP Option 66, length 19: "tftp://192.168.5.1/"
            Default-Gateway Option 3, length 4: 192.168.5.254
            NTP Option 42, length 4: 192.168.5.1
            END Option 255, length 0
23:30:15.111344 IP (tos 0x0, ttl 32, id 56702, offset 0, flags [DF], proto UDP (17), length 567)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:04:f2:a6:7b:0c (oui Unknown), length 539, xid 0x9249903d, Flags [none] (0x0000)
          Client-Ethernet-Address 00:04:f2:a6:7b:0c (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Request
            Requested-IP Option 50, length 4: 192.168.0.88
            Server-ID Option 54, length 4: masada
            MSZ Option 57, length 2: 1492
            Parameter-Request Option 55, length 11:
              Subnet-Mask, BR, Option 160, TFTP
              Default-Gateway, Time-Server, NTP, Time-Zone
              Domain-Name-Server, Domain-Name, LOG
            Hostname Option 12, length 20: "Polycom_0004f2a67b0c"
            Vendor-Class Option 60, length 120: "^@^@6=s^A^GPolycom^B^USoundPointIP-SPIP_321^C^P2345-12360-001,1^D^_SIP/4.0.11.0583/21-Jun-16 17:15^E^^UP/5.0.11.0282/08-Jun-16 19:39"
            T125 Option 125, length 120: 13885,1929447248,1869379939,1869414933,1399813486,1682993001,1853114704,760434761,1348416306,822284338,859059501,825373494,808267824,824979716,525551952,791948848,774975790,808794163,791818541,1249209901,825630769,926560565,85874000,792014384,774975790,808597554,791689261,1249209901,825630769,960115513
            END Option 255, length 0
23:30:15.151171 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.88 tell 0.0.0.0, length 46
23:30:15.654544 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.88 is-at 00:04:f2:a6:7b:0c (oui Unknown), length 46
23:30:15.806440 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has masada tell 192.168.0.88, length 46

TIA,

Chris

[SteffenBaierUK]

Hello Chris_,

welcome to the Polycom Community.

We would need to see some phone logs and other things so please go ahead and raise this with your reseller.

The phone is question was sold back in 03/09/2010 so it is well out of warranty. You can contact NETXUSA for a Pay Per Incident / PPI ticket.

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

[Anonymous]

---

>>SteffenBaierUK wrote:

>>We would need to see some phone logs and other things so please go ahead and raise this with your reseller.

I have the log level raised on the cfg log as well as several others. This phone does not appear to have a dhcpc log, but the net log does show some of what is happening. The phone seems to regularly fail to delay long enough to receive a reply to the arp ping it sends to locate the dhcp server.

FTR: There is no reseller involved here, so I posted here thinking that this was a "community" forum.

>>The phone is question was sold back in 03/09/2010 so it is well out of warranty. You can contact NETXUSA for a Pay Per Incident / PPI ticket.

I have no plans to use PPI services. Your reply leads me to believe that this is not a "community" forum, but rather an advertising service for Polycom's support services.

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

This was not a helpful response and did not "solve" my issue.

[SteffenBaierUK]

Hello Chris_,

You are free to post within this community anything you want. In addition all community members or guests are free to respond to yourself.

If a issue requires Polycom's attention to fix an issue then the "normal" support process works. 

• If a unit is within warranty you can open a free ticket via your Polycom reseller.
• If a unit is outside warranty and the problem is not easily reproduced you have to go the PPI way.

This works the same for any other service organisation.

The Phones original owner purchased this from / via NextUSA back in 2010 so if this was yourself it would be in your interest to get this fixed / looked at.

If you are not interested or you are not the original owner of the phone you can wait until someone else responds.

Best Regards

Steffen Baier

Polycom Global Services