- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ip udp-bcast-forward
Switches, Hubs, and Modems
1752584
Members
4316
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2007 06:27 AM
тАО07-17-2007 06:27 AM
Hi!
If the command "ip udp-bcast-forward" is really required to be able to use the command "-protocol udp < ip-address >
< port-number | port-name >"?
My configuration looks up to now thus and
works:
ip routing
vlan 21
name "QS"
ip helper-address 172.16.100.206
ip forward-protocol udp 172.16.100.206 4011
ip forward-protocol udp 172.16.100.206 tftp
ip address 172.16.21.1 255.255.255.0
exit
Which function has "ip udp-bcast-forward"?
If the command "ip udp-bcast-forward" is really required to be able to use the command "-protocol udp < ip-address >
< port-number | port-name >"?
My configuration looks up to now thus and
works:
ip routing
vlan 21
name "QS"
ip helper-address 172.16.100.206
ip forward-protocol udp 172.16.100.206 4011
ip forward-protocol udp 172.16.100.206 tftp
ip address 172.16.21.1 255.255.255.0
exit
Which function has "ip udp-bcast-forward"?
cm60
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2007 07:30 PM
тАО07-23-2007 07:30 PM
Solution
"Syntax [no] ip udp-bcast-forward. Enables or disables UDP broadcast forwarding on the router. Routing must be enabled before executing this command."
Quoted from this:
ftp://ftp.hp.com/pub/networking/software/6400-5300-4200-3400-AdvTrafficMgmt-Oct2006-59906051-Chap11.pdf
Quoted from this:
ftp://ftp.hp.com/pub/networking/software/6400-5300-4200-3400-AdvTrafficMgmt-Oct2006-59906051-Chap11.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2007 06:56 AM
тАО07-26-2007 06:56 AM
Re: ip udp-bcast-forward
Hi Olaru Dan!
The routing is or was on. The question is, Why must I give the order " ip-udp-bcast- forward " if already the order " ip forward-protocol udp is sufficient 172.16.100.206 4011 " to the activation of the function?
The routing is or was on. The question is, Why must I give the order " ip-udp-bcast- forward " if already the order " ip forward-protocol udp is sufficient 172.16.100.206 4011 " to the activation of the function?
cm60
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2008 01:27 AM
тАО06-30-2008 01:27 AM
Re: ip udp-bcast-forward
Config as in Admin Guide
cm60
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP