>From CCO:
port block
Use the port block interface configuration command to block the
flooding of unknown unicast or multicast packets to a port. Use the no
form of this command to resume normal forwarding.
port block {unicast | multicast}
no port block {unicast | multicast}
Syntax Description unicast
Packets with unknown unicast addresses are not forwarded to this port
multicast
Packets with unknown multicast addresses are not forwarded to this
port.
Now, what do they mean by unknown multicast addresses? I'm not a
server guy so I don't know much about Norton Ghost, but I'm assuming the
multicast application supports joining and leaving the multicast group.
If that's the case then either CGMP or IGMP snooping by the switch would
block undesired multicast traffic to non-participating ports, anyway.
Your idea might work, I just am still pondering how they decide what an
'unknown' multicast address is in the first place.
Maybe after I finish my second cup of coffee it will occur to me. <g>
John
>>> "Stuart Pittwood" <[EMAIL PROTECTED]> 3/26/01 8:35:37 AM >>>
Heads up ... Newbie question coming your way.
We have a 2924M-XL-EN
On fastethernet 0/1 is an NT4 Server
On fastethernet 0/2 is a link to another hub which has a group of
clients .. All running an app from the NT4 server
We regularly have to ghost machines (which are connected to the other
ports), we ghost using the multicast method.
The multicasting has negative effects on the clients running this app
from the NT4 box.
If I were to use the port block multicast command on 0/1 & 0/2 would
this isolate ghost's multicast traffic from those ports thus solving
my
problem?
Thanks in advance
Stu
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
