Unsolved

This post is more than 5 years old

184 Posts

18062

January 8th, 2006 02:00

6024 UDP Relay doesnt work

Hello all, i have run into a snag with a 6024 and UDP broadcast packets.
This switch is at the core of a decent size network with 15 edge switches connecting to it with 15 vlans and the associated routing between the vlans.
 
some of the applications running the servers/machines use UDP broadcast packets on various ports to support a server browser function. My issue is i have enabled the UDP broadcast helper function with the appropriate port listed.
 
source ip interface         UDP destination port             destination address
 
255.255.255.255                    1000                                    255.255.255.255
 
The above is an example of a line in the UDP relay table. From my understanding this should broadcast any UDP packet destined for port 1000 from any interface. However the switch doesnt seem to be forwarding the packets. I can see the activity on the port from where the packets originates, but i dont see it being broadcasted to the other interfaces.
 
Can you see anything obviously wrong. I am running the newest firmware on the switch.
 
Thanks
 
          

January 10th, 2006 11:00

I forward your question to a colleague of mine and his answer is pasted below.  I hope this helps.

Cuong.

=====

The help on the webpage is incorrect.

The destination IP address must be a subnet broadcast address. The switch must have an IP address on the subnet destination address.

Here is an example CLI:

interface range ethernet g(2-5)

switchport mode general

exit

vlan database

vlan 2-5

exit

interface ethernet g2

switchport general pvid 2

exit

interface ethernet g3

switchport general pvid 3

exit

interface ethernet g4

switchport general pvid 4

exit

interface ethernet g5

switchport general pvid 5

exit

interface ethernet g2

switchport general allowed vlan add 2

exit

interface ethernet g3

switchport general allowed vlan add 3

exit

interface ethernet g4

switchport general allowed vlan add 4

exit

interface ethernet g5

switchport general allowed vlan add 5

exit

interface vlan 2

ip address 10.10.2.210 255.255.255.0

exit

interface vlan 3

ip address 10.10.3.210 255.255.255.0

exit

interface vlan 4

ip address 10.10.4.210 255.255.255.0

exit

interface vlan 5

ip address 10.10.5.210 255.255.255.0

exit

ip helper-address all 10.10.2.255 1000

p helper-address all 10.10.3.255 1000

ip helper-address all 10.10.4.255 1000

ip helper-address all 10.10.5.255 1000

Message Edited by DELL-Cuong N. on 01-10-2006 07:51 AM

January 10th, 2006 13:00

I believe the other "helper-address" command must be executed within an IP interface so it is less global then the "ip helper-address" command.

As for the other part of your question, the best way to see if it would work as you suggested is to try it.  I'm not near a lab right now otherwise I would just try it myself :-).

Cuong.

BTW here is a link to the manual pages around this command:
 

Message Edited by DELL-Cuong N. on 01-10-2006 09:15 AM

184 Posts

January 10th, 2006 13:00

Ok, so from what i see there the udp relay is being broken down into individual subnet entries. But is there a way to do more of a global relay? lets say for example all the interfaces ip's on the switch are
 
vlan1 - 192.168.0.x  255.255.255.0
vlan2 - 192.168.1.x  255.255.255.0
 
ect...
 
And the actual interface address on each vlan is 192.168.x.1
 
If we have an ip helper entry as follows should it work?
 
ip helper address all 192.168.255.255 1000
 
Will this forward udp broadcasts on port 1000 from any of the interfaces to all of the 192.168.x.x interfaces?
 
 
I also noticed a command that appears more global, it appears to function in a similar way and it is called the "helper address". Is this maybe what i need to be using?
 
Thanks again

1 Message

January 10th, 2006 17:00

I'm working with Dr.No this network so I'll toss my question in to the arena myself.

Is there a simpler way to specify a port range then in a invidual port by port basis?

The applications that will be going across the network use a broad range of ports (on average 10-15 per application) with no defined notes on what ports are tied to what function of the applications.

184 Posts

January 10th, 2006 18:00

Disregard that last post as you answered my question in the previous response. I just wasnt paying attention:smileywink:

 

Thank you for your help

January 10th, 2006 18:00

My colleague has some follow up response for your question DRN010.
 
In response to your question regarding the following command:

 ip helper address all 192.168.255.255 1000

 Will this forward udp broadcasts on port 1000 from any of the interfaces to all of the 192.168.x.x interfaces?

The answer is:

 No. The destination must be a broadcast address on a known interface. 

On the question regarding the "helper-address" command.  The "ip helper-address" command works for all interfaces whereas the "helper-address" command works on a per IP interface basis only.  The "interface" level helper-address command takes precedence over the global "ip helper-address" command but since the "ip helper-address" command works on all interfaces it is less maintenance as new interfaces are added.

In response to "ceown" who asked about the port list.  The port list is given as a list of ports.  There is no range syntax.  Also there is a limit of 128 address/port pairs total.  Meaning you can specify up to 128 ip/port combinations only.  So don't just define ports that you don't use and don't define entries for IP network that you don't use to limit this configuration to only what you need because you will run out of entries.

Cuong.

 

184 Posts

January 10th, 2006 18:00

Thanks for the reply, i plan on trying that tonight.  If this does need to be done individually, with 15 interfaces i will have 15 entries for each port.  In the manual they specify a maximum of 128 address port pairs. Are those classified as 1 entry? So i could only potentially enter a maximum of 8 port to be broadcasted across the 15 interfaces? Yikes i hope not.

 

 

 

184 Posts

January 11th, 2006 02:00

Well after pulling out my hair tonight i am at a loss as to why this wont work. afte trying all sort of ports and interface addresses, it still appears that the switch/router is dropping the packet. I can sniff the traffic from the client and confirm the packet is heading to the switch. I even see the activity light on the appropriate port. However i dont see any activity on the server vlan. I must be missing something simple so i figured i should post the config incase anyone can see a silly mistake. Sorry about the long post, i tried to clean it up as best i could to keep it short. Is there by chance any sort of debug mode similar to a cisco product so i can analyze what is happening to the packet?

Thanks

 

# show run


Router Configuration
-----------------------------

no spanning-tree
interface port-channel 1
description "Core uplink"
interface port-channel 2
description "Core uplink"
interface port-channel 3
description "switch 6"
interface port-channel 4
description "switch 7"
interface port-channel 5
description "switch 8"
interface port-channel 6
description "switch 9"
interface port-channel 7
description "switch 10"
interface port-channel 1
switchport mode trunk
interface port-channel 2
switchport mode trunk
interface port-channel 3
switchport mode trunk
interface port-channel 4
switchport mode trunk
interface port-channel 5
switchport mode trunk
interface port-channel 6
switchport mode trunk
interface port-channel 7
switchport mode trunk

interface range ethernet g(23-24)
switchport mode trunk
vlan database
vlan 10,20,30,40,50,60,70,80,90,100,110,120,130,140,150,200
interface range port-channel 1
switchport trunk allowed vlan add 10
interface range port-channel 1
switchport trunk allowed vlan add 20
interface range port-channel 1
switchport trunk allowed vlan add 30
interface range port-channel 1
switchport trunk allowed vlan add 40
interface range port-channel 1
switchport trunk allowed vlan add 50
interface range port-channel 3
switchport trunk allowed vlan add 60
interface range port-channel 4
switchport trunk allowed vlan add 70
interface range port-channel 5
switchport trunk allowed vlan add 80
interface range port-channel 6
switchport trunk allowed vlan add 90
interface range port-channel 7
switchport trunk allowed vlan add 100
interface range port-channel 2
switchport trunk allowed vlan add 110
interface range port-channel 2
switchport trunk allowed vlan add 120
interface range port-channel 2
switchport trunk allowed vlan add 130
interface range port-channel 2
switchport trunk allowed vlan add 140
interface range port-channel 2
switchport trunk allowed vlan add 150
interface range ethernet g(9-10)
switchport access vlan 200
interface range ethernet g(23-24)
switchport trunk allowed vlan add 200
interface range port-channel (1-2)
switchport trunk allowed vlan add 200

interface vlan 10
name switch 1
interface vlan 20
name swtich 2
interface vlan 30
name switch 3
interface vlan 40
name switch 4
interface vlan 50
name switch 5
interface vlan 60
name switch 6
interface vlan 70
name switch 7
interface vlan 80
name switch 8
interface vlan 90
name switch 9
interface vlan 100
name switch 10
interface vlan 110
name switch 11
interface vlan 120
name switch 12
interface vlan 130
name switch 13
interface vlan 140
name switch 14
interface vlan 150
name switch 15
interface vlan 200
name Servers

interface range ethernet g(1-4)
channel-group 1 mode on
interface range ethernet g(5-8)
channel-group 2 mode on
interface range ethernet g(13-14)
channel-group 3 mode on
interface range ethernet g(15-16)
channel-group 4 mode on
interface range ethernet g(17-18)
channel-group 5 mode on
interface range ethernet g(19-20)
channel-group 6 mode on
interface range ethernet g(21-22)
channel-group 7 mode on

ip igmp snooping
interface vlan 1
ip igmp snooping
interface vlan 10
ip igmp snooping
interface vlan 20
ip igmp snooping
interface vlan 50
ip igmp snooping
interface vlan 80
ip igmp snooping
interface vlan 90
ip igmp snooping
interface vlan 100
ip igmp snooping
interface vlan 130
ip igmp snooping
interface vlan 150
ip igmp snooping
interface vlan 200
ip igmp snooping

interface vlan 1
ip address 172.0.0.101 255.255.255.0
interface vlan 10
ip address 10.10.10.1 255.255.255.0
interface vlan 20
ip address 10.10.20.1 255.255.255.0
interface vlan 30
ip address 10.10.30.1 255.255.255.0
interface vlan 40
ip address 10.10.40.1 255.255.255.0
interface vlan 50
ip address 10.10.50.1 255.255.255.0
interface vlan 60
ip address 10.10.60.1 255.255.255.0
interface vlan 70
ip address 10.10.70.1 255.255.255.0
interface vlan 80
ip address 10.10.80.1 255.255.255.0
interface vlan 90
ip address 10.10.90.1 255.255.255.0
interface vlan 100
ip address 10.10.100.1 255.255.255.0
interface vlan 110
ip address 10.10.110.1 255.255.255.0
interface vlan 120
ip address 10.10.120.1 255.255.255.0
interface vlan 130
ip address 10.10.130.1 255.255.255.0
interface vlan 140
ip address 10.10.140.1 255.255.255.0
interface vlan 150
ip address 10.10.150.1 255.255.255.0
interface vlan 200
ip address 10.10.200.1 255.255.255.0

interface ip 10.10.10.1
directed-broadcast
interface ip 10.10.20.1
directed-broadcast
interface ip 10.10.30.1
directed-broadcast
interface ip 10.10.40.1
directed-broadcast
interface ip 10.10.50.1
directed-broadcast
interface ip 10.10.60.1
directed-broadcast
interface ip 10.10.70.1
directed-broadcast
interface ip 10.10.80.1
directed-broadcast
interface ip 10.10.90.1
directed-broadcast
interface ip 10.10.110.1
directed-broadcast
interface ip 10.10.120.1
directed-broadcast
interface ip 10.10.130.1
directed-broadcast
interface ip 10.10.140.1
directed-broadcast
interface ip 10.10.150.1
directed-broadcast
interface ip 10.10.200.1
directed-broadcast

ip route 0.0.0.0 0.0.0.0 10.10.200.254 metric 10
router ospf redistribute static
router ospf redistribute connected
router ospf router-id 172.0.0.254
ip dhcp relay address 10.10.200.100
ip dhcp relay enable
no router rip redistribute static

interface ip 10.10.10.1
rip
rip version 2
interface ip 10.10.20.1
rip
rip version 2
interface ip 10.10.30.1
rip
rip version 2
interface ip 10.10.40.1
rip
rip version 2
interface ip 10.10.50.1
rip
rip version 2
interface ip 10.10.60.1
rip
rip version 2
interface ip 10.10.70.1
rip
rip version 2
interface ip 10.10.80.1
rip
rip version 2
interface ip 10.10.90.1
rip
rip version 2
interface ip 10.10.100.1
rip
rip version 2
interface ip 10.10.110.1
rip
rip version 2
interface ip 10.10.120.1
rip
rip version 2
interface ip 10.10.130.1
rip
rip version 2
interface ip 10.10.140.1
rip
rip version 2
interface ip 10.10.150.1
rip
rip version 2
interface ip 10.10.200.1
rip
rip version 2
interface ip 172.0.0.101
rip
rip version 2

ip helper-address all 10.10.200.100 37 42 49 53 137 138
ip helper-address all 10.10.200.255 10777
interface vlan 1
ip igmp
ip igmp last-member-query-interval 0 1

hostname "CORE"
____________________________
>> Default settings:
_____________________________

>> Router Configuration
-----------------------------

>> SW version 2.0.0.01 (date  10-Apr-2005 time  08:28:21)

>> Gigabit Ethernet Ports
=============================
>> no shutdown
>> speed 1000
>> duplex full
>> negotiation
>> flow-control off
>> mdix auto
>> no back-pressure

>> interface vlan 1
>> interface port-channel 1 - 7

>> no router RIP

>> no router OSPF enable

>> spanning-tree
>> spanning-tree mode STP

>> qos basic


>> exit

January 11th, 2006 12:00

Hi, I will contact you via email directly.  I would like to get some more info from you that's hard to post on the forum.

Cuong.

184 Posts

March 9th, 2006 18:00

Just want to thank Dell and some of the Mods on this forum for giving us a hand with this issue. Turns out we actually found a bug which will be fixed in the next firmware release.

 

Thanks Again

 

 

0 events found

No Events found!

Top