I have verified by running Ethereal on the DFM Server that it is receiving IfDown Traps from various switches but these events are not being shown\coming up in the "Alerts and Activities" ? All these interfaces were put in "Un-Managed" state by default.
Does an Interface has to be in the "Managed State" before DFM will act on any Trap specific to that interface ?
If Yes then How can I make a Bulk Change to convert all the "Trunk Interfaces\Ports" to Managed State ?
What criteria does DFM follow, when discovering an interface and putting it into a Managed state instead of Un-Managed ?
Yes, an interface must be in a managed state before DFM will process any new events for that interface. Bulk management is not easily doable in DFM 2.x. In LMS 3.0, DFM 3.0 comes with bulk manage/unmanage scripts. For now, you will have to use the Detailed Device View, and go through each interface one-by-one.
Trunk ports are put in a managed state by default. However, a DFM trunk port is not the same as a dot1q or ISL trunk port. DFM considers a port to be a trunk port if it is connected to another device that DFM is managing.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...