Priscilla,

Well, it�s been an interesting project.  Unfortunately, the DHCP server app
that I wound up trying (Vicomsoft) was so buggy that I couldn�t keep it from
crashing.  Even when it was running, it was highly, highly unstable. 
Granted, it was a demo, but I would think a demo would have basic
functionality.

Furthermore, I couldn�t get into the console port of the 2900XL.  Tried
everything.  The darned port is fried.

So�here is what I came up with:


                           2621
                            |
                            |  <--100Mb/s dot1q trunk
                            |
                 Foundry Networks switch
                  |                  |
                  |                  |  <--100Mb/s access ports
                  |                  |
              DHCP Serv          DHCP Client


The 2621, with 64M of memory and 8M of flash, is running 12.1-18 IP Plus.  I
don�t know much about the Foundry switch.  It was straight out of the box
just yesterday.  I configured it with a dot1q trunk to the router, an access
port in vlan 100 (192.168.1.0/24), and an access port in vlan 200
(192.168.2.0/24).  The server (192.168.1.100) was attached to VLAN 100 and
the client (192.168.2.?) to vlan 200.  The router subinterfaces were the .1
address.  Subinterface F0/0.2 had an IP helper address of 192.168.1.100.

On a couple of occasions I moved the client to vlan 100.  The server did
actually work two or three times with a local client.  It never once worked
with a non-local client.  The good news is that the DHCP Discovery crossed
the vlans via the 2621 and looked to be in pretty good shape:

 Frame 44 (343 bytes on wire, 343 bytes captured)
    Arrival Time: Dec 21, 2002 18:01:21.694951000
    Time delta from previous packet: 0.721309000 seconds
    Time relative to first packet: 40.720429000 seconds
    Frame Number: 44
    Packet Length: 343 bytes
    Capture Length: 343 bytes
Ethernet II, Src: 00:02:fd:1d:c0:20, Dst: 00:08:74:03:77:b5
    Destination: 00:08:74:03:77:b5 (Dell_Com_03:77:b5)
    Source: 00:02:fd:1d:c0:20 (Cisco_1d:c0:20)
    Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.2.1 (192.168.2.1), Dst Addr:
192.168.1.100 (192.168.1.100)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
        0000 00.. = Differentiated Services Codepoint: Default (0x00)
        .... ..0. = ECN-Capable Transport (ECT): 0
        .... ...0 = ECN-CE: 0
    Total Length: 329
    Identification: 0x0061
    Flags: 0x00
        .0.. = Don't fragment: Not set
        ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 255
    Protocol: UDP (0x11)
    Header checksum: 0x358d (correct)
    Source: 192.168.2.1 (192.168.2.1)
    Destination: 192.168.1.100 (192.168.1.100)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootps (67)
    Source port: bootps (67)
    Destination port: bootps (67)
    Length: 309
    Checksum: 0xde84 (correct)
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 1
    Transaction ID: 0xcb4d080c
    Seconds elapsed: 17250
    Bootp flags: 0x8000 (Broadcast)
        1... .... .... .... = Broadcast flag: Broadcast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 192.168.2.1 (192.168.2.1)
    Client hardware address: 00:06:5b:e4:d3:97
    Server host name not given
    Boot file name not given
    Magic cookie: (OK)
    Option 53: DHCP Message Type = DHCP Discover
    Unknown Option Code: 251 (1 bytes)
    Option 61: Client identifier
        Hardware type: Ethernet
        Client hardware address: 00:06:5b:e4:d3:97
    Option 50: Requested IP Address = 192.168.1.2
    Option 12: Host Name = "laprmccarverGFE"
    Option 60: Vendor class identifier = "MSFT 5.0"
    Option 55: Parameter Request List
        1 = Subnet Mask
        15 = Domain Name
        3 = Router

Notice the relay agent address of 192.168.2.1.  That bodes well.  However,
for some reason, this was the response:

Frame 45 (70 bytes on wire, 70 bytes captured)
    Arrival Time: Dec 21, 2002 18:01:21.695010000
    Time delta from previous packet: 0.000059000 seconds
    Time relative to first packet: 40.720488000 seconds
    Frame Number: 45
    Packet Length: 70 bytes
    Capture Length: 70 bytes
Ethernet II, Src: 00:08:74:03:77:b5, Dst: 00:02:fd:1d:c0:20
    Destination: 00:02:fd:1d:c0:20 (Cisco_1d:c0:20)
    Source: 00:08:74:03:77:b5 (Dell_Com_03:77:b5)
    Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.1.100 (192.168.1.100), Dst Addr:
192.168.2.1 (192.168.2.1)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
        0000 00.. = Differentiated Services Codepoint: Default (0x00)
        .... ..0. = ECN-Capable Transport (ECT): 0
        .... ...0 = ECN-CE: 0
    Total Length: 56
    Identification: 0x015b
    Flags: 0x00
        .0.. = Don't fragment: Not set
        ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: ICMP (0x01)
    Header checksum: 0xb4b4 (correct)
    Source: 192.168.1.100 (192.168.1.100)
    Destination: 192.168.2.1 (192.168.2.1)
Internet Control Message Protocol
    Type: 3 (Destination unreachable)
    Code: 3 (Port unreachable)
    Checksum: 0x1cbd (correct)
    Internet Protocol, Src Addr: 192.168.2.1 (192.168.2.1), Dst Addr:
192.168.1.100 (192.168.1.100)
        Version: 4
        Header length: 20 bytes
        Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
            0000 00.. = Differentiated Services Codepoint: Default (0x00)
            .... ..0. = ECN-Capable Transport (ECT): 0
            .... ...0 = ECN-CE: 0
        Total Length: 329
        Identification: 0x0061
        Flags: 0x00
            .0.. = Don't fragment: Not set
            ..0. = More fragments: Not set
        Fragment offset: 0
        Time to live: 255
        Protocol: UDP (0x11)
        Header checksum: 0x358d (correct)
        Source: 192.168.2.1 (192.168.2.1)
        Destination: 192.168.1.100 (192.168.1.100)
    User Datagram Protocol, Src Port: bootps (67), Dst Port: bootps (67)
        Source port: bootps (67)
        Destination port: bootps (67)
        Length: 309
        Checksum: 0xde84

I�m convinced it was the server app.  So if someone can point me to a better
one, I�ll just bet this will work fine.  I didn�t think to try it without IP
Plus.  Would you like me to?  The truth is, trunking support/functionality
seems to be on a case-by-case basis where the 2600s are concerned.

Scott



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=59724&t=59724
--------------------------------------------------
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