3com 4500 vlan's ACL's

[bornpilot]

Greetings,

I have a bit of an issue with my 3com switch. I have two vlans--10 and 20. the subnets are 10.0.0.0/23 and 10.0.2.0/23 respectively. I have a default gateway setup to point to my firewall 10.0.1.254.

On the switch I have two vlan interfaces configured 10.0.1.253 and 10.0.2.253 respective to the vlans. On my dchp server I have two pool setup one for each subnet. I have created some ports on the switch untagged to vlan 10 and untagged to vlan 20.

Vlan 20 is used for Voip and I have an Avaya ip office on vlan 20 with an ip addy of 10.0.3.254. If I plug a client into a port for vlan 10 my dhcp works correct and gives me an ip addy for subnet 10.0.0.0/23. The same for if I plug a client into vlan 20--I get an ip for subnet 10.0.2.0/23.

My issue is this: I have the management software for the Avaya IP office on vlan 10 and I need to access the ip office on vlan 20. I am unable to get any connection from vlan 10 to vlan 20--except for dhcp.

When I have client plugged into vlan 10 I can connect to the vlan 20 interface but I unable to access the ip office on vlan 20. If I have a client plugged into vlan 20 I have no problem getting to ip office box, but my management software needs to be on vlan 10.

On the switch I have a routes from:

[4500]display ip routing-table 
 Routing Table: public net
Destination/Mask   Protocol Pre  Cost        Nexthop         Interface
0.0.0.0/0          STATIC   60   0           10.0.1.254      Vlan-interface10
10.0.0.0/23        DIRECT   0    0           10.0.1.253      Vlan-interface10
10.0.1.253/32      DIRECT   0    0           127.0.0.1       InLoopBack0
10.0.2.0/23        DIRECT   0    0           10.0.3.253      Vlan-interface20
10.0.3.253/32      DIRECT   0    0           127.0.0.1       InLoopBack0
127.0.0.0/8        DIRECT   0    0           127.0.0.1       InLoopBack0
127.0.0.1/32       DIRECT   0    0           127.0.0.1       InLoopBack0

I am not sure if the issue is with routing -- since dhcp server works I don't think that, I think it might be an ACL issue.
Sincerely,

Tim Turner

 

[Bas1234]

Tried to do a route add?

On your Avaya manager pc open a dos box type;

route add 10.0.3.0 mask 255.255.255.0 10.x.x.x -p

10.x.x.x is your interface on the routing switch.
The -p is to make in permanent. This way you have it more secure because no one else can go into you Voice VLAN.

What also works is making the Manager PC static, and for the Gateway address use the Interface of the routing switch, you probaly have your router there.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________