Thank you Marko. On Wed, Jan 11, 2012 at 2:07 PM, Marko Milivojevic <[email protected]>wrote:
> I would clarify with the proctor for sure. > > -- > Marko Milivojevic - CCIE #18427 (SP R&S) > Senior CCIE Instructor - IPexpert > > On Wed, Jan 11, 2012 at 12:03, marc abel <[email protected]> wrote: > > Ok thank you, this makes sense. So if in the lab they give us an > imaginary > > device to create a binding for then this would probably be the format, > > unless they specify otherwise. > > > > > > On Wed, Jan 11, 2012 at 1:39 PM, Marko Milivojevic <[email protected]> > > wrote: > >> > >> On Wed, Jan 11, 2012 at 11:30, marc abel <[email protected]> wrote: > >> > Is there an obvious way to determine a client identifier from the MAC > >> > address, other than looking at the DHCP bindings? > >> > >> You can run "debug ip dhcp server events" and "debug ip dhcp server > >> packets" on the router configured as the server and you will see > >> incoming requests there. Otherwise, bindings is the only place to find > >> it. > >> > >> However, *if* the client is using MAC address to form a client-id, > >> which is not a requirement, it will, as a rule, be <media type><mac > >> address>. For Ethernet (and 802.11[abng]), "media type" will be 01. > >> IOS will then insert dots after every two bytes, so for your > >> CC1E.CC1E.CC1E MAC address, client-id will become 01CC.1ECC.1ECC.1E. > >> > >> -- > >> Marko Milivojevic - CCIE #18427 (SP R&S) > >> Senior CCIE Instructor - IPexpert > > > > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
