Sometimes customers are unaware about their own network. For example, we need SMTP credentials for Layer 2 switches to do automatic discovery of network devices. Sometimes the network management teams are unaware of their SMTP credentials because the teams have been shuffled since the network was deployed. Or sometimes, when we support our government and defense customers, they don't have clearance to share these credentials with us. Some of the features, such as auto discoverability, get hampered if the customer is not aware of their own network or somehow can't share privileges and credentials with our tool for them to work properly. Not in ManageEngine NetFlow Analyzer in particular, but there are other features of the OpManager suite that could afford to be updated. There is something called a CLI, command-line interface, that allows us to configure network devices such as switches. This is old technology. This product suite has CLI-based configurations, but as of last year, most network devices come with Zero Touch Provisioning (ZTP). OpManager does not support this functionality, and we don't really have a timeline on when ZTP functionality will be available. In ManageEngine NetFlow Analyzer, we have to set custom thresholds to get alerted if there is a problem in network connectivity. It would be helpful if we could automate the tool such that we don't have to set thresholds manually, and the tool automatically alerts us when it detects issues. When experts deploy this tool, we already know what thresholds should be normal. But customers in general may not have this skill set. For newer customers who need to adopt this product, an automated method of alerting would definitely be beneficial.
Network Troubleshooting involves analyzing, diagnosing, and resolving problems within a network to ensure smooth operation and accessibility. Professionals in this field look at hardware, software, and communication issues to maintain network integrity.Network Troubleshooting is an essential practice for maintaining operational efficiency and minimizing downtime. It involves identifying the root cause of network failures, performance bottlenecks, and security breaches, ensuring that network...
Sometimes customers are unaware about their own network. For example, we need SMTP credentials for Layer 2 switches to do automatic discovery of network devices. Sometimes the network management teams are unaware of their SMTP credentials because the teams have been shuffled since the network was deployed. Or sometimes, when we support our government and defense customers, they don't have clearance to share these credentials with us. Some of the features, such as auto discoverability, get hampered if the customer is not aware of their own network or somehow can't share privileges and credentials with our tool for them to work properly. Not in ManageEngine NetFlow Analyzer in particular, but there are other features of the OpManager suite that could afford to be updated. There is something called a CLI, command-line interface, that allows us to configure network devices such as switches. This is old technology. This product suite has CLI-based configurations, but as of last year, most network devices come with Zero Touch Provisioning (ZTP). OpManager does not support this functionality, and we don't really have a timeline on when ZTP functionality will be available. In ManageEngine NetFlow Analyzer, we have to set custom thresholds to get alerted if there is a problem in network connectivity. It would be helpful if we could automate the tool such that we don't have to set thresholds manually, and the tool automatically alerts us when it detects issues. When experts deploy this tool, we already know what thresholds should be normal. But customers in general may not have this skill set. For newer customers who need to adopt this product, an automated method of alerting would definitely be beneficial.