So, you're turning up a new connection with 2100 customers on it (or ARP entries at least) and DHCP is slowing right down?
If I understand this right, this is normal behaviour.... on one of our cable routers (CTMS router) when we do maintenance and bring 500+ customers back online, it takes a good 20 minutes for all those customers to get an IP address again. Once we're beyond that initial startup it works great though.... Does that seem similiar to your situation or does DHCP just choke all together? Paul -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neal Rauhauser Sent: Thursday, May 17, 2007 11:32 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] 12.3.22 lawful intercept on 7206 - DHCP bug eats 2,000+ customers I have a 7206 with NPE-G1, upgraded from 12.2.15T11 last night to 12.3.22 lawful intercept and simultaneously taking from 256m to 1024m of memory. The system has BGP peers and a couple of thousand DSL customers attached (I know, I know, OS and memory upgrade are part of me splitting it for this customer). We watched 2,100 ARP entries appear for the ATM PVCs this morning and all seemed well but the onboard DHCP was sick. We do a 'show run' and it'll fail with a "try later" or it'll run but it takes several minutes to generate anything. We're on the phone with TAC now and we've got someone clueful but this is incredibly painful for the customer - anyone seen this thing before? Suggestions? _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/