The Network Management SNMP Resources Tab was updated!
SNMP MIB Repositories
[HTML] - MIBSearch.COM
[HTML] - SNMPLink.ORG [Brocade|Cisco|Extreme|Juniper|Standards]
[HTML] - OIDView.com [on-line application]
SNMP Network Management Platforms
[HTML] - HP Network Node Manager 9i
HP Network Node Manager - Data Sheets
[PDF] HP Network Management Center
[PDF] HP Network Node Manager (NNMi) Software
[PDF] HP Solutions for Automated Network Management
[PDF] HP NNMi Data Sheet
[HTML] NP NNMi Manuals
[HTML] HP NNMi 9.1 Supported Device Matrix
[HTML] HP NNMi 9.0 Supported Device Matrix
HP Network Node Manager - Specifications
[HTML] HP NNMi 9.10 (Advanced)
[HTML] HP NNM iSPI for IP Multicast 9.10
[HTML] HP NNM iSPI for IP Telephony 9.10
[HTML] HP NNM iSPI for MPLS 9.10
[HTML] HP NNM iSPI Performance for Metrics 9.10
[HTML] HP NNM iSPI Performance for Quality Assurance 9.10
[HTML] HP NNM iSPI Performance for Traffic 9.10
Showing posts with label Network Node Manager. Show all posts
Showing posts with label Network Node Manager. Show all posts
Friday, May 18, 2012
Thursday, May 17, 2012
HP Network Node Manager 9.10i - A Quick Analysis
HP Network Node Manager 9.10i - A Quick Analysis
Abstract:
For as long as there was communications over wires, Network Management existed. With the advent of SNMP, management could become sophisticated enough to allow for proactive management of intelligent devices and the health of various resources they managed. HP's Network Node Manager, considered "the gold standard" in network management, continues to upgrade their platform with newer features.
Key Information:
Real information on Network Node Manager is available in various datasheets and specification pages. What separates HP's Network Node Manager from the rest of the competition includes:
Everyone who wants to be a managed services provider plays in the Linux space, but only development houses truly capable of supporting large telco environments play in the UNIX space. Solaris is the dominate market leader, with more installations than IBM AIX and HP-UX combined, but HP-UX is still supported (for the time being - their Itanium based HP-UX platform is at-risk.)
Scalability of 25K devices with 1M interfaces is a terrific improvement, over the old days of HP Network Node Manager. The older NNM platforms seemed to become sluggish between 1,000 and 2,000 devices. Modern day telco managed services engagements regularly deal with multiple core devices have 1,000,000 interfaces per core device (not to mention end-points) - which this writer was able to do a half-decade ago with EMC Ionix on an old 8 socket UltraSPARC IV platform (as well as other customers.) Running a separate NNM instance for every internal core device is completely unrealistic. Most people do not consider the vertical scalability needs of network management tools - single customers with large interface counts MUST support large socket counts on UNIX systems like Solaris and HP-UX to meet the business requirements.
With 0-overhead virtualization technologies like Solaris Zones, Node Manager is able to play "in the big leagues" with managed service providers, to provide simplistic multi-tenant solutions where overlapping ip addresses must be managed. Each Solaris Zone can route to a different customer, with identical IP Addresses - with no cost in system resources, since Solaris Zones all share the same kernel resources.
Authentication of users to an external LDAP directory provides for Single Sign-On capabilities and resolves a variety of issues with auditing requirements, password changing issues, locking out users who are no longer with the service provider, etc.
It is critical for a managed services organization to understand whether a device can be monitored and managed. Clear documentation, which is available for the world to see, provides that kind of feedback to the community, to level-set expectations with telco providers to communicate to joint customers.
Embedded Postgres and third-party Oracle are both supported, the former for service providers to avoid Oracle service provider fees, the latter for enterprises with few DBA resources to provide singular database support across an entire enterprise.
Multi-Tenant requirements are tremendously diverse. The new web interface offers configuration, like the old X-Windows interface, but the data-sheets are strangely silent about SNMPv3 support - an absolute minimum for dealing with multi-tenancy, so customers know their data is secure during the traversal of shared networks. Any security minded individual be concerned about support or robustness of support of SNMPv3 by this product.
Additional Information
See the SNMP Resources Tab on the Network Management Blog for more information.
Abstract:
For as long as there was communications over wires, Network Management existed. With the advent of SNMP, management could become sophisticated enough to allow for proactive management of intelligent devices and the health of various resources they managed. HP's Network Node Manager, considered "the gold standard" in network management, continues to upgrade their platform with newer features.
Key Information:
Real information on Network Node Manager is available in various datasheets and specification pages. What separates HP's Network Node Manager from the rest of the competition includes:
- Multi-Platform Support
Solaris, Linux, Windows, and HPUX.
Solaris support provided for Managed-Services grade, Linux for Enterprise grade, Windows for Small-Medium Business grade network management needs. - Robust Performance
Single station capable of 25,000 devices, up to 1,000,000 interfaces. - Robust Virtualization
HP Network Node Manager supports Zones under Solaris - providing Solaris based Managed Service Providers with secure multi-tenancy at 0% systems overhead penalty. - External Authentication
Users and Roles can be mapped to an LDAP directory - Excellent Device Certification Documentation
Clear on-line documentation regarding which device and features are supported. - Database Support
Embedded Postgres and third-party Oracle are both supported. - Multi-Tenancy Interface
Network Node Manager old interface offered this, the new one offers this, as well. - Encryption and SNMPv3
The old Network Node Manager did not offer SNMPv3 encryption, without a proxy from SNMP Research. The data sheets do not clearly indicate SNMPv3 encryption support under multi-tenancy and security.
Everyone who wants to be a managed services provider plays in the Linux space, but only development houses truly capable of supporting large telco environments play in the UNIX space. Solaris is the dominate market leader, with more installations than IBM AIX and HP-UX combined, but HP-UX is still supported (for the time being - their Itanium based HP-UX platform is at-risk.)
Scalability of 25K devices with 1M interfaces is a terrific improvement, over the old days of HP Network Node Manager. The older NNM platforms seemed to become sluggish between 1,000 and 2,000 devices. Modern day telco managed services engagements regularly deal with multiple core devices have 1,000,000 interfaces per core device (not to mention end-points) - which this writer was able to do a half-decade ago with EMC Ionix on an old 8 socket UltraSPARC IV platform (as well as other customers.) Running a separate NNM instance for every internal core device is completely unrealistic. Most people do not consider the vertical scalability needs of network management tools - single customers with large interface counts MUST support large socket counts on UNIX systems like Solaris and HP-UX to meet the business requirements.
With 0-overhead virtualization technologies like Solaris Zones, Node Manager is able to play "in the big leagues" with managed service providers, to provide simplistic multi-tenant solutions where overlapping ip addresses must be managed. Each Solaris Zone can route to a different customer, with identical IP Addresses - with no cost in system resources, since Solaris Zones all share the same kernel resources.
Authentication of users to an external LDAP directory provides for Single Sign-On capabilities and resolves a variety of issues with auditing requirements, password changing issues, locking out users who are no longer with the service provider, etc.
It is critical for a managed services organization to understand whether a device can be monitored and managed. Clear documentation, which is available for the world to see, provides that kind of feedback to the community, to level-set expectations with telco providers to communicate to joint customers.
Embedded Postgres and third-party Oracle are both supported, the former for service providers to avoid Oracle service provider fees, the latter for enterprises with few DBA resources to provide singular database support across an entire enterprise.
Multi-Tenant requirements are tremendously diverse. The new web interface offers configuration, like the old X-Windows interface, but the data-sheets are strangely silent about SNMPv3 support - an absolute minimum for dealing with multi-tenancy, so customers know their data is secure during the traversal of shared networks. Any security minded individual be concerned about support or robustness of support of SNMPv3 by this product.
Additional Information
See the SNMP Resources Tab on the Network Management Blog for more information.
Labels:
HP,
HPUX,
Network Node Manager,
Network Management,
Solaris
Friday, May 11, 2012
HP Network Node Manager 9.10i - WhyUpgrade?
HP Network Node Manager 9.10i - WhyUpgrade?
Abstract:
Reasons to move from NNM 7 to NNM 9i: completely web based, scales even better, bundled virtualization technologies, and smart plugins for enhanced capabilities. A company called Pepperweed created additional value-add technology referred to as "ePacks". The ePacks provide a fixed price skew which include best practice implementation, including: knowledge pack. The Pepperweed representative indicates that ePacks are designed to get you up and running in under a week
Video:
The following video introduces the Pepperweed CTO and allows him to introduce his product with NNM 9i to the general network management community.
[埋込みオブジェクト:http://c.brightcove.com/services/viewer/federated_f9?isVid=1&isUI=1]
[Pepperweed CTO, Alex Ryals, introduced NNMi platform and their product]
Data Sheets and Specification:
See the SNMP Resources Tab on the Network Management blog for more details.
Thursday, November 18, 2010
Simulating OpenView Events With Net-SNMP SNMP Traps
Simulating OpenView Events With via Net-SNMP SNMP Traps
Abstract:
HP OpenView Network Node Manager used to be the industry standard network management tool. Net-SNMP is the standard SNMP stack used on most operating systems, such as Solaris. There is still a need to simulate the platform for migration of infrastructure. One common way to simulate the HP OpenView Network Node Manager environment is through the use of OpenView Events (ovevent) and Net-SNMP SNMP Traps (snmptrap) commands.
OpenView Events
The HP OpenView Node Down Event can be simulated through a guaranteed transport via the "ovevent" command.
ovevent $Severity $NMS \ .1.3.6.1.4.1.11.2.17.1.0.$Event \ .1.3.6.1.4.1.11.2.17.2.1.0 Integer 14 \ .1.3.6.1.4.1.11.2.17.2.2.0 OctetString ${Node}Simulate Using Net-SNMP via SNMP V1 Trap
NMS = IP or Resolvable Name of Network Management Station
Node = IP or Resolvable Name of the Managed Device
Severity = Critical, Major, Minor, Info
Event = 58916865 [OV_Node_Down], 58916864 [OV_Node_Up]
An SNMP V1 trap can be produced to closel simulate this Node Down event. Note, this is not the exact representation, nor is the delivery of the event guaranteed. An SNMP Trap Receiver must receive this.
snmptrap -v 1 -c $Community $NMS \Simulate Using Net-SNMP via SNMP V2c Trap
.1.3.6.1.4.1.11.2.17.1 ${Node} 6 58916865 0
Community= SNMP Community String on used on Network Managment Station
An SNMP V2c trap can be produced to closel simulate this Node Down event. Note, this is not the exact representation, nor is the delivery of the event guaranteed. An SNMP Trap Receiver must receive this.
snmptrap -v 2c -c $Community $NMS \Simulate Using Net-SNMP via SNMP V2c Trap Test Tool
0 .1.3.6.1.4.1.11.2.17.1.0.58916865 \
.1.3.6.1.4.1.11.2.17.2.1.0 i 14 \
.1.3.6.1.4.1.11.2.17.2.2.0 s $Node
An SNMP V2c trap can be produced to closel simulate this Node Down event. Note, this is not the exact representation, nor is the delivery of the event guaranteed. An SNMP Trap Receiver must receive this.
snmptest -v 2c -c $Community $NMS:162 \<\<\!Conclusion:
\$T
.1.3.6.1.2.1.1.3.0
t
0
.1.3.6.1.6.3.1.1.4.1.0
o
.1.3.6.1.4.1.11.2.17.1.0.58916865
i
0
.1.3.6.1.4.1.11.2.17.2.1.0
i
14
.1.3.6.1.4.1.11.2.17.2.2.0
s
$Node
\!
Common events from HP OpenView Network Node Manager, the former "gold standard" in Network Management, can be simulated under stock Solaris 10 and Solaris 11 with simple available OS commands.
Subscribe to:
Comments (Atom)