it does not.
even if you put the span port in the same bridge group as the firewall's
port, it still acts like a switch,
a seperate collision domain between each port and node.
why not just put the fw on a hub, and the monitoring
station on the hub. And connect the hub to the 2648G_L3 ?
I've thought of putting it on a hub but its a production network and I don't
want to add another point of failure. If something happened to the hub it
would bring the whole network down.
Brunner Joseph wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
it does not.
even if you
to be honest... this is how we operate... Hubs are much less likely to fail
that switches. I mean...really...the only thing that could fry is the power
supply... :)
I can't believe the 2948 l3 does not support port monitoring... that's
insane...That needs to be a support call. That is
The hub itself might not fail, but it would be one more thing that should
be on a UPS. We had a five-hour power outage last night and learned the
hard way about the holes in our disaster recovery plan. In our case, we
do have our main hub on a UPS but the darn UPS failed. That hub is in a
Its kind of a hybrid. It is a 50 port switch, but they are all routed ports
and are configured like a router. You need to make bridge-groups and place
interfaces inside the groups inorder to create VLANs. Still I really think
they should've have added this feature as it can be very helpful and
2948-L3-1(config-if)#rmon ?
native Monitor the interface in native mode
promiscuous Monitor the interface in promiscuous mode
Off hours, im going to do some tests for you, with the device,
these commands and traffic director, and sniffer.
I will let you know. From Cisco's site and
6 matches
Mail list logo
