Recent content by bill2455

Sorry about that, I was giving an update on progress. in addition to asking the question if any one had any input on this topic ? the method from "P Multicast Helper-map - Converting Broadcast and Multicast" would require at least two routers between the two switches? In the Lab - I only have...

Vlan 1 was not receiving the broadcast packets - 1st issue UDP frames where not getting through to Vlan-1, in the process of receiving UDP packets the TTL=1 settings, needed to change to TTL=254 for multicast. Packets are now seen although still being dropped by the switch. 1) The L3 switch...

Vlan 1 was not receiving the broadcast packets - 1st issue UDP frames where not getting through to Vlan-1, in the process of converting broadcast-to-mulitcast packets the TTL=1 settings, needed to change to TTL=254 for multicast. Packets are now seen although still being dropped by the switch...

To answer your question: We have opened TAC agreement with Cisco on this issue now: we have a ticket open on the current TTL issue: The current status is we are experience an TTL issue on the 128 network; we have been told we need to deploy forwarding rather than routing UDP packets between...

I have the 10 getting everything as its should, the 128 network I'm having TTL issues. I can ping it fine from the 10 network. any one seen this type of TTL problem when forwarding UDP traffic between two Vlans on different subnets within the same site before ? Bill

Port #5 was bad - so i used port #6 under the same config. I have the reader Tx UDP/IP packet/frames and can receive the data on my laptop when on the same Vlan, device IP address (10.10.63.3) Vlan 63, with SVI 63 set to (10.10.63.1. - 255.255.255.0) My objective is to receive UDP data on the...

wouldn't Vlan 63 forward or route to Vlan 1 by default in its current config ?

Switch port # 5 it was indeed - tks

None taken, and we have under way: I have a shoot out for an experienced L3 switch "CCIE" consultant for this implementation in the Chicago/Indianapolis area. 2455:)

tangoseal - thanks for the reply - We just order in a switch for ourselves to work with in the lab, although we didn't get TAC. We may consider doing so in the future. Thanks for the links - good data links - I have a call-out for Cisco Certified "CCIE" consultant on this L3 switch subject...

in my config file - Vlan 1 and Vlan 63 - ip routing is configured if the reader is connected to vlan 63/port #5 or 6 and the app server is connected to Vlan 1 any other ports other than ports 5 and 6 on the same L3 3750x 24p-switch - should be able to receive the data being sent from the reader...

Back when I was testing the L3 switch connected on the network - we later found out there was an routing table and access list connected to issue of (UDP) traffic being blocked (as it was being considered broadcasting and denied) - as a security measure to block any possibility of getting DoS...

the initial testing between both (Vlan 1 and Vlan 63) are on the same switch; the reader devices on Vlan63 (10.10.63.2 and 3 - 10.10.63.1) connected to ports 5 & 6 configured will be routing UDP/IP traffic to Vlan 1(128.1.1.100 - 128.1.1.161) configured for port #10 on the same L3 switch. The...