Priscilla,

I haven’t forsaken you (yet).  But here’s the deal:  

My 2610 only has 24M of memory.  I ignored the recommendation for at least
40M to run 12.1 IP Plus only to meet with disastrous results.  I need IP
Plus on this old clunker to enable dot1q (and I’m pretty sure at least 12.1
also).  So...I found what appears to be a 2620 in one of our labs.  There’s
a 2900XL nearby.  I suspect I can fire the two up and get ‘em going. 
However, the only module in the 2900 uplink slot is GigE.  So does anyone
know if I can configure one of the 24 access ports to trunk?  I have minimal
experience with the 2900XL and that was over a year ago.

The real problem is that I don’t have any servers in that lab at the
moment.  Does anyone know of a simple stand-alone DHCP application that will
run on a Windows machine?  If not, the best I can do at the moment using a
2600 would be to put a sniffer on 192.168.1.0 and a client on 192.168.2.0. 
The captured DHCP client requests should show whether or not the pertinent
subinterface address is being plugged into giaddr.
 
Regards,

Scott   



s vermill wrote:
> 
> Priscilla,
> 
> I'm sure someone can verify this with a 2600 specifically.  As
> far as DHCP in general, yes.  We just did this with a much
> larger 6509-based network.  No problems.  The only difference,
> of course, is that the MSFC has virtual router interfaces per
> VLAN - not subinterfaces on a router on a stick.  Can't see why
> DHCP itself would know or care.  But I guess you can't know for
> sure what that subinterface on the 2600 will do until someone
> specifically verifies it.  If you don't get such a response,
> I've got a 2600 laying around at the moment.  I'll dig up a
> switch, set up a DHCP server, and mock 'er up for ya.  Won't
> take long at all.
> 
> Regards,
> 
> Scott
> 
> 




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=59684&t=59578
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to