Dhcp Error In Pkt. Punting
IP isWhoisCalculatorTool PointsNewsNews tip?ForumsAll ForumsHot TopicsGalleryInfoHardwareAll FAQsSite FAQDSL FAQCable TechAboutcontactabout uscommunityISP FAQAdd ISPISP Ind. ForumsJoin Search similar:bought a Cisco 3845 for $85, hows it look?[Config] Slow Internet issue...Cisco SAP-1602i connected to 2960 trunk port[Internet] Did I mess up my modem?[DSL] Help to configure: SmartRG (routing mode) + router Forums → Equipment Support → Hardware By Brand → Cisco → Cisco 2911 15.2(1)T1 cannot pull DHCP address uniqs3726 Share « FW STP? • [Config] BGP over GRE » macallahjoin:2003-01-22Wichita Falls, TX macallah Member 2013-Mar-6 1:14 am Cisco 2911 15.2(1)T1 cannot pull DHCP addressThe config for the interface is below and the log output from debug dhcp. I cannot figure out why it rejects the DHCP reply. nothing else on the network seems to have trouble getting a dhcp address.interface GigabitEthernet0/2 no ip dhcp client request tftp-server-address ip address dhcp client-id GigabitEthernet0/2 no ip redirects no ip unreachables no ip proxy-arp ip flow ingress ip flow egress ip nat outside ip virtual-reassembly in ip tcp adjust-mss 1452 duplex auto speed auto!When it goes to get an address it says:000097: Mar 5 23:31:56.811 CST: DHCP: Try 1 to acquire address for GigabitEthernet0/2000098: Mar 5 23:31:56.815 CST: DHCP: allocate request000099: Mar 5 23:31:56.815 CST: DHCP: new entry. add to queue, interface GigabitEthernet0/2000100: Mar 5 23:31:56.815 CST: DHCP: Client socket is opened000101: Mar 5 23:31:56.815 CST: DHCP: SDiscover attempt # 1 for entry:000102: Mar 5 23:31:56.815 CST: DHCP: SDiscover: sending 316 byte length DHCP packet000103: Mar 5 23:31:56.815 CST: DHCP: SDiscover 316 bytes000104: Mar 5 23:31:56.815 CST: B'cast on GigabitEthernet0/2 interface from 0.0.0.0000105: Mar 5 23:31:58.775 CST: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up000106: Mar 5 23:31:58.811 CST: DHCP: Received a BOOTREP pkt000107: Mar 5 23:31:58.811 CST: DHCP: Error in pkt. punting000108: Mar 5 23:31:59.775 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2,
features CCIE forums and discussions for all tracks including Routing & Switching, Voice, Security, Service Provider, Wireless,, and Storage. Through these online communities you can discuss your questions with thousands of your peers, hundreds of CCIE's and INE's own team of world renowned CCIE instructors and authors, Brian Dennis - Quintuple CCIE #2210, Brian McGahan – Triple CCIE #8593, Petr Lapukhov - Quad CCIE #16379, and Mark Snow - Dual CCIE #14073. Home CCIE Forums Forums » INE Products » CCIE Routing & Switching Lab Workbook Volume II Version 5.0 » IEWB-RS http://www.dslreports.com/forum/r28073237-Cisco-2911-15-2-1-T1-cannot-pull-DHCP-address Volume 2 Version 5 Lab 13 » Task 7.4 DHCP Latest post 11-28-2012 2:02 PM by rwalker@us.fujitsu.com. 14 replies. Page 1 of 1 (15 items) Sort Posts: Oldest to newest Newest to oldest Previous Next 09-27-2010 4:13 AM martind Joined on 07-30-2010 Associate Points 115 Task 7.4 DHCP Reply Contact I don't understand why the solution for this task is to configure R6 as "ip helper" ? http://ieoc.com/forums/thread/119368.aspx Only connection to DHCP server is through R3… so there is no redundancy in topology. My solution is to configure only R3 as "ip helper" without "redundancy" keyword. The solution from SG goes again task 6.4 that states "Assume R3 is the only device allowed to relay DHCP messages"Martin
Post Points: 35 11-07-2010 7:48 AM In reply to rkosylu1 Joined on 01-22-2010 Professional Points 1,675 Re: Task 7.4 DHCP Reply Contact For the testing example in the solution guide, to get SW2's VALN-367s SVI ipaddress via dhcp, the trunk port between SW1-2 needs to be set to dhcp snooping trust mode, else it can only get the ipaddress via R3 and not R6. Post Points: 20 12-06-2010 10:39 AM In reply to jchan Joined on 01-11-2009 Elite Points 9,560 Re: Task 7.4 DHCP Reply Contact Thanks rkosylu1!!! Indeed, ip dhcp snooping trust is needed between sw1 and sw2 trunk. Thanks for your inputs and comments. INE staff, can you please include this in the next udpate? CCIE #29342 (R&S) Post Points: 20 12-06-2010 7:57 PM In reply to Petr Lapukhov Joined on 07-05-2008 Elite Points 6,470 Re: Task 7.4 DHCP Reply Contact hmm makes sense, what's the trunking port numRouting & SwitchingCCNP SecurityCCNP WirelessCCIPCCIECisco Networking AcademySafariAuthorsChapters & ArticlesExploreAboutAffiliatesNewslettersPressPromotionsSalesSeriesUser Groups Home > Articles > Cisco Network Technology > General Networking > Cisco Firewall Configuration Fundamentals Cisco Firewall Configuration Fundamentals By Alexandre M.S.P. Moraes. Sample Chapter is http://www.ciscopress.com/articles/article.asp?p=1722547&seqNum=9 provided courtesy of Cisco Press. Date: Jul 8, 2011. SaveDiggDel.icio.usPrintEmail Chapter Information Contents Device Access Using the CLI Basic ASA Configuration Basic FWSM Configuration Remote Management Access to ASA and FWSM IOS Baseline Configuration Remote Management Access to IOS Devices Clock Synchronization Using NTP Obtaining an IP Address Through the PPPoE Client DHCP Services dhcp error Summary Further Reading Chapter Description This chapter describes the configuration fundamentals for IOS and ASA-based firewalls, highlighting the similarities between the product families. From the Book Cisco Firewalls $55.99 (Save 20%) This chapter covers the following topics: Device access using the CLI Basic ASA configuration Basic FWSM configuration Remote management access to ASA and FWSM dhcp error in IOS Baseline configuration Remote management access to IOS devices Clock synchronization using NTP Obtaining an IP address through the PPPoE client DHCP services "All rising to great places is by a winding stair." --Francis Bacon After the introductory lessons of the first two chapters, it is time to begin the practical work with the Cisco Classic Network Firewalls. This chapter focuses on topics such as IP address assignment, Command Line Interface (CLI) usage and how to prepare the devices to be remotely managed using protocols such as Telnet, Secure Shell (SSH) and HTTPS. The contents presented are simple, so if you are already familiar with Cisco Classic Firewalls, you can skip this chapter altogether. If you are just beginning, this chapter's topics are relevant and helpful. Device Access Using the CLI Even when planning to manage a Cisco Firewall using a Graphical User Interface (GUI), you probably need to take some initial configuration steps via the CLI. The good news, in this