Link to home
Start Free TrialLog in
Avatar of techneitsolutions
techneitsolutionsFlag for Belgium

asked on

Vlan routing problem on 3com 4924 switch

Hi,

The company bought a 4924 switch to divide the diffirent departments into vlans.
I'm testing out the switch and was able to create the vlans 2 and 3
Vlan 3 contains 10 ports.

The inteface of the vlan ip is 192.168.1.1 when I connect a client to one of the ports I have to give it an IP address manually, is there a way that this can be done by dhcp?

The main problem is that I can connect from the client to the switch but I cannot connect to an outside address.
The switch main's ip adres is 192.168.169.250, this address is randomly chosen.
I can tracert that ip (the tracert process is extremely slow) but when I try to tracert the ip-address of the router (192.168.169.254) it times out.

In the routing table 192.168.169.254 is defined as default gateway.

Can somebody help me solving this problem?
Avatar of Busbar
Busbar
Flag of Egypt image

is this switch a layer 3 switch if not u will need a router to do the work
Avatar of techneitsolutions

ASKER

The com 4924 is indeed a layer 3 switch
Avatar of pseudocyber
pseudocyber

Sometimes you have to turn the routing process on with a manual command, like Cisco's "ip routing" command.

Also, sometimes in order for routing to occur on an l3 switch, the switch has to see an active interface in the source and destination VLAN to bring it "up".

From the IP's you've provided, it looks like you're using a 16 bit mask - is this the case?!?
When I connect a laptop to the switch on a port not assigned to a vlan I have to give it an ipaddress manually and from that point everything works fine, it's just when I plug it to a port that's member of a vlan and i give it an ipaddress that I can't access the internet.
ASKER CERTIFIED SOLUTION
Avatar of pseudocyber
pseudocyber

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If I tracert 192.168.169.250 the tracert finishes succesfully

If I tracert 192.168.169.254 the tracert stops at the ip 192.168.1.1 (which is the on of the vlan) if I recall well.
If I tracert 192.168.169.250 the tracert finishes succesfully

If I tracert 192.168.169.254 the tracert stops at the ip 192.168.1.1 if I recall well (192.168.1.1 is the ip of the vlan)
Could you explain your vlans, the IP networks, and the physical topology?

Ie:  VLAN 1, Net 10.1.1.0/24, Gateway 10.1.1.1 (virtual interface on vlan 1 on switch 1)
I'll get back to my office asap.
I'll let you know in about 45 minutes
Hi,

The configuration is
3com router local ip 192.168.169.254
The switch main's ip adres is 192.168.169.250
VLAN3 192.168.1.1 with subnetmask 255.255.255.0

What's strange is that I first define a vlan (the only thing I have to do in this state is select the ports)
and then I add an IP interface (ip address, subnet mask, vlan id,type of ip-address)

So Interface 3 is part of VLAN3 and received ip address 192.168.1.1

Routing table:

destination     subnet mask     gateway

Default route    ---                   192.168.169.254
192.168.1.0     255.255.255.0   ---
192.168.101.0 255.255.255.0   ---
192.168.169.0 255.255.255.0   ---

I don't know why 192.168.101.0 is there it has something to do with a default defined IP Interface
, it says IP Interface 2 Type SLIP ip address 192.168.101.1 ....

When I tracert 192.168.169.250 it takes a while (several seconds) but the trace works.

If I tracert 192.168.169.254 I get response

1 2ms 2ms 3ms 192.168.1.1
2  *      *     *   Request Timed Out
3com support engineer found the answer
what was the problem ?