Hi Sundeep Dsouza   Could you resolve your issue?     I could see the following with the info of your debug:   - You have a SVI Vlan 155 with IP address 172.13.1.2 - Inside the SVI 155 you had configured two IP helper-address:  192.168.11.10 and 192.168.11.11 - DHCP Server return you the IP Address 192.168.15.50 mask 255.255.255.0 - An error occured because an ARP issue. It cannot install that IP address that reside in another network (SIOCSARP ioctl failed (error 22).)     Please check: - from DHCP Server: Assignation based on MAC Address or Client ID for endpoint with issues. - a subnet overlapping or related misconfiguration    ... View more

Checking this DHCP case issue, the reason is because the DHCP server is allocating those devices as Static and assign a large number in  Renewal time and Rebind time.   My case (Autonomous AP 3502 IOS Version 15.2(4)JB6): *Jul 8 08:05:16.088: DHCP: Try 23 to acquire address for BVI1 *Jul 8 08:05:16.088: DHCP: allocate request *Jul 8 08:05:16.088: DHCP: new entry. add to queue, interface BVI1 *Jul 8 08:05:16.088: DHCP: Client socket is opened *Jul 8 08:05:16.088: DHCP: SDiscover attempt # 1 for entry: *Jul 8 08:05:16.088: Temp IP addr: 0.0.0.0 for peer on Interface: BVI1 *Jul 8 08:05:16.088: Temp sub net mask: 0.0.0.0 *Jul 8 08:05:16.088: DHCP Lease server: 0.0.0.0, state: 3 Selecting *Jul 8 08:05:16.088: DHCP transaction id: 1D97 *Jul 8 08:05:16.088: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs *Jul 8 08:05:16.088: Next timer fires after: 00:00:04 *Jul 8 08:05:16.088: Retry count: 1 Client-ID: 0006.f6c8.e0d7 *Jul 8 08:05:16.088: Client-ID hex dump: 0006F6C8E0D7 *Jul 8 08:05:16.088: Hostname: ap *Jul 8 08:05:16.088: DHCP: SDiscover placed class-id option: 436973636F204150206333353030 *Jul 8 08:05:16.088: DHCP: SDiscover: sending 287 byte length DHCP packet *Jul 8 08:05:16.088: DHCP: SDiscover 287 bytes *Jul 8 08:05:16.088: B'cast on BVI1 interface from 0.0.0.0 *Jul 8 08:05:16.516: DHCP: Received a BOOTREP pkt *Jul 8 08:05:16.516: DHCP: Scan: Message type: DHCP Offer *Jul 8 08:05:16.516: DHCP: Scan: Server ID Option: 192.168.10.10 = C0A80A0A *Jul 8 08:05:16.516: DHCP: Scan: Lease Time: 4294967295 *Jul 8 08:05:16.516: DHCP: Scan: Renewal time: 429496729 *Jul 8 08:05:16.516: DHCP: Scan: Rebind time: 4294966 *Jul 8 08:05:16.516: DHCP: Scan: Subnet Address Option: 255.255.255.0 *Jul 8 08:05:16.516: DHCP: Scan: Renewal time larger than Rebind time *Jul 8 08:05:16.516: DHCP: Error in pkt. punting   Eliminating the static DHCP to this Autonomus AP, received its IP Address.   *Jul 8 08:24:59.876: DHCP: SDiscover attempt # 1 for entry: *Jul 8 08:24:59.876: Temp IP addr: 0.0.0.0 for peer on Interface: BVI1 *Jul 8 08:24:59.876: Temp sub net mask: 0.0.0.0 *Jul 8 08:24:59.876: DHCP Lease server: 0.0.0.0, state: 3 Selecting *Jul 8 08:24:59.876: DHCP transaction id: 17B1 *Jul 8 08:24:59.876: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs *Jul 8 08:24:59.876: Next timer fires after: 00:00:04 *Jul 8 08:24:59.876: Retry count: 1 Client-ID: 0006.f6c8.e0d7 *Jul 8 08:24:59.876: Client-ID hex dump: 0006F6C8E0D7 *Jul 8 08:24:59.876: Hostname: ap *Jul 8 08:24:59.876: DHCP: SDiscover placed class-id option: 436973636F204150206333353030 *Jul 8 08:24:59.876: DHCP: SDiscover: sending 287 byte length DHCP packet *Jul 8 08:24:59.876: DHCP: SDiscover 287 bytes *Jul 8 08:24:59.876: B'cast on BVI1 interface from 0.0.0.0 *Jul 8 08:24:59.885: DHCP: Received a BOOTREP pkt *Jul 8 08:24:59.885: DHCP: Scan: Message type: DHCP Offer *Jul 8 08:24:59.885: DHCP: Scan: Server ID Option: 192.168.10.10 = C0A80A0A *Jul 8 08:24:59.885: DHCP: Scan: Lease Time: 86400 *Jul 8 08:24:59.885: DHCP: Scan: Renewal time: 43200 *Jul 8 08:24:59.885: DHCP: Scan: Rebind time: 75600 *Jul 8 08:24:59.885: DHCP: Scan: Subnet Address Option: 255.255.255.0 *Jul 8 08:24:59.885: DHCP: Scan: Router Option: 192.168.10.1 *Jul 8 08:24:59.885: DHCP: Scan: DNS Name Server Option: 192.168.10.1 *Jul 8 08:24:59.885: DHCP: Scan: Vendor specific option 43: C0A80AC9 *Jul 8 08:24:59.885: DHCP: rcvd pkt source: 192.168.10.10, destination: 255.255.255.255 *Jul 8 08:24:59.885: UDP sport: 43, dport: 44, length: 300 *Jul 8 08:24:59.885: DHCP op: 2, htype: 1, hlen: 6, hops: 0 *Jul 8 08:24:59.885: DHCP server identifier: 192.168.10.10 *Jul 8 08:24:59.885: xid: 17B1, secs: 0, flags: 8000 *Jul 8 08:24:59.885: client: 0.0.0.0, your: 192.168.10.105 *Jul 8 08:24:59.885: srvr: 0.0.0.0, gw: 0.0.0.0 *Jul 8 08:24:59.885: options block length: 52 *Jul 8 08:24:59.885: DHCP Offer Message Offered Address: 192.168.10.105 *Jul 8 08:24:59.885: DHCP: Lease Seconds: 86400 Renewal secs: 43200 Rebind secs: 75600 *Jul 8 08:24:59.885: DHCP: Server ID Option: 192.168.10.10 *Jul 8 08:24:59.885: DHCP: offer received from 192.168.10.10 *Jul 8 08:24:59.885: DHCP: SRequest attempt # 1 for entry: *Jul 8 08:24:59.885: Temp IP addr: 192.168.10.105 for peer on Interface: BVI1 *Jul 8 08:24:59.885: Temp sub net mask: 255.255.255.0 *Jul 8 08:24:59.885: DHCP Lease server: 192.168.10.10, state: 4 Requesting *Jul 8 08:24:59.885: DHCP transaction id: 17B1 *Jul 8 08:24:59.885: Lease: 86400 secs, Renewal: 0 secs, Rebind: 0 secs *Jul 8 08:24:59.885: Next timer fires after: 00:00:03 *Jul 8 08:24:59.885: Retry count: 1 Client-ID: 0006.f6c8.e0d7 *Jul 8 08:24:59.885: Client-ID hex dump: 0006F6C8E0D7 *Jul 8 08:24:59.888: Hostname: ap *Jul 8 08:24:59.888: DHCP: SRequest- Server ID option: 192.168.10.10 *Jul 8 08:24:59.888: DHCP: SRequest- Requested IP addr option: 192.168.10.105 *Jul 8 08:24:59.888: DHCP: SRequest placed class-id option: 436973636F204150206333353030 *Jul 8 08:24:59.888: DHCP: SRequest: 299 bytes *Jul 8 08:24:59.888: DHCP: SRequest: 299 bytes *Jul 8 08:24:59.888: B'cast on BVI1 interface from 0.0.0.0 *Jul 8 08:24:59.891: DHCP: Received a BOOTREP pkt *Jul 8 08:24:59.891: DHCP: Scan: Message type: DHCP Ack *Jul 8 08:24:59.891: DHCP: Scan: Server ID Option: 192.168.10.10 = C0A80A0A *Jul 8 08:24:59.891: DHCP: Scan: Lease Time: 86400 *Jul 8 08:24:59.891: DHCP: Scan: Renewal time: 43200 *Jul 8 08:24:59.891: DHCP: Scan: Rebind time: 75600 *Jul 8 08:24:59.891: DHCP: Scan: Subnet Address Option: 255.255.255.0 *Jul 8 08:24:59.891: DHCP: Scan: Router Option: 192.168.10.1 *Jul 8 08:24:59.891: DHCP: Scan: DNS Name Server Option: 192.168.10.1 *Jul 8 08:24:59.891: DHCP: Scan: Vendor specific option 43: C0A80AC9 *Jul 8 08:24:59.891: DHCP: rcvd pkt source: 192.168.10.10, destination: 255.255.255.255 *Jul 8 08:24:59.891: UDP sport: 43, dport: 44, length: 300 *Jul 8 08:24:59.891: DHCP op: 2, htype: 1, hlen: 6, hops: 0 *Jul 8 08:24:59.891: DHCP server identifier: 192.168.10.10 *Jul 8 08:24:59.891: xid: 17B1, secs: 0, flags: 8000 *Jul 8 08:24:59.891: client: 0.0.0.0, your: 192.168.10.105 *Jul 8 08:24:59.891: srvr: 0.0.0.0, gw: 0.0.0.0 *Jul 8 08:24:59.891: options block length: 52 *Jul 8 08:24:59.891: DHCP Ack Message *Jul 8 08:24:59.891: DHCP: Lease Seconds: 86400 Renewal secs: 43200 Rebind secs: 75600 *Jul 8 08:24:59.891: DHCP: Server ID Option: 192.168.10.10 *Jul 8 08:25:00.719: %SYS-5-CONFIG_I: Configured from console by console *Jul 8 08:25:01.873: %LINK-6-UPDOWN: Interface BVI1, changed state to up *Jul 8 08:25:02.873: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up *Jul 8 08:25:02.892: DHCP: Releasing ipl options: *Jul 8 08:25:02.892: DHCP: Applying DHCP options: *Jul 8 08:25:02.892: Setting default_gateway to 192.168.10.1 *Jul 8 08:25:02.892: Adding default route 192.168.10.1 *Jul 8 08:25:02.924: DHCPC: Notifying other components about option 43 *Jul 8 08:25:02.924: Allocated IP address = 192.168.10.105 255.255.255.0 *Jul 8 08:25:02.924: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.10.105, mask 255.255.255.0, hostname ap ... View more

was this issue solved? ... View more

Just one of them is virtual. Apparently is not a sync problems, but a possible bug CSCuh70984 is hitting. Although is not discarded the delay issue between the nodes (200 ms), maybe is not the problem. We will do the workaround if the problem is resolved. I'll let you know guys. Kevin ... View more

Hi James, Sorry for answer a little late. I  had not the information before by the client. The connection between the two sites is a International MPLS (no internet from our perspective). This is the information: BW: 2 Mbps Delay: 200 ms I put the 2 Nodes ISE in that way: Node in Europe (We will call NodeA): - Administration (PAN) Primary - Monitoring (MNT) - Policy (PSN) - NTP Server: Public NTP Server. 130.206.3.166 Timezone: UTC CA Certificate: Self-Certificate_from_ise_node_America Node in America (We will call NodeB): - Administration (PAN) Secondary NTP Server: Public NTP Server. 130.206.3.166 (the same NTP Server) Timezone: EST The NodeB is registered from NodeA using its dns name, with no problem (so I assumed that the certificate, credential and DNS resolve correctly). Waiting for a couple of hour, the NodeB viewed from the NodeA in the section Administration - System - Deployment state OUT OF SYNC. When I tried to sync manually, the NodeA showed the following message: " Internal Error: Server returned HTTP Response Code: 500 for URL: https://NodeB/deployment-rpc/cert Expiry status " And happened everytime I tried to sync. The NodeB is no possible to access through http server web page correctly after its register. It shows the portal page, but it doesn't matter if you use a correct user or bad user, after you click Logging, return a white page without information. The solution to use the same timezone I will put in practice, making the nodes using for both UTC. If you guys have another ideas, it's appreciate it. Thanks, ... View more

The direction of the Cisco logo for the Cisco Aironet 1040, 1140, 3500i Series has the position Ө= 90 and  Ф=90 ? Anyone know this? ... View more

Hi everyone, I have the same doubt. I did a ip sla configuration on 1841 and 7206VXR and don't show nothing in one-way delay. ----------------------7206--------------------- -ip sla monitor responder -ip sla monitor 1 - type jitter dest-ipaddr 10.9.105.14 dest-port 16384 source-ipaddr 10.8.20.102  codec g711alaw - tos 184 -ip sla monitor schedule 1 start-time now -ntp peer 10.9.105.14 HOST)#show ip sla sta Round Trip Time (RTT) for       Index 1         Latest RTT: 507 milliseconds Latest operation start time: 10:57:36.619 UTC Sun Oct 10 2010 Latest operation return code: OK RTT Values:         Number Of RTT: 1000             RTT Min/Avg/Max: 125/507/846 milliseconds Latency one-way time:         Number of Latency one-way Samples: 0         Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds         Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds Jitter Time:         Number of Jitter Samples: 999         Source to Destination Jitter Min/Avg/Max: 1/1/6 milliseconds         Destination to Source Jitter Min/Avg/Max: 1/5/23 milliseconds Packet Loss Values:         Loss Source to Destination: 0           Loss Destination to Source: 0         Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0 Voice Score Values:         Calculated Planning Impairment Factor (ICPIF): 17         Mean Opinion Score (MOS): 3.84 Number of successes: 38 Number of failures: 0 Operation time to live: 1347 sec -------------------------1841------------------------------- -ip sla monitor responder -ip sla monitor 1 - type jitter dest-ipaddr 10.8.20.102 dest-port 16384 source-ipaddr 10.9.105.14 codec g711alaw - tos 184 -ip sla monitor schedule 1 start-time now -ntp peer 10.8.20.102 3383)#show ip sla monitor statistic Round trip time (RTT)   Index 1         Latest RTT: 614 ms Latest operation start time: 10:50:50.491 UTC Wed Oct 27 2010 Latest operation return code: OK RTT Values         Number Of RTT: 999         RTT Min/Avg/Max: 347/614/867 ms Latency one-way time milliseconds         Number of one-way Samples: 0         Source to Destination one way Min/Avg/Max: 0/0/0 ms         Destination to Source one way Min/Avg/Max: 0/0/0 ms Jitter time milliseconds         Number of SD Jitter Samples: 997         Number of DS Jitter Samples: 998         Source to Destination Jitter Min/Avg/Max: 0/6/19 ms         Destination to Source Jitter Min/Avg/Max: 0/1/3 ms Packet Loss Values         Loss Source to Destination: 1           Loss Destination to Source: 0         Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0 Voice Score Values         Calculated Planning Impairment Factor (ICPIF): 20 MOS score: 3.72 Number of successes: 32 Number of failures: 0 Operation time to live: 1668 sec ... View more