Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Managing SNMP v1 NETOPIA Routers Using NCM Fails Due to FIPS Compliance

Managing SNMP v1 NETOPIA Routers Using NCM Fails Due to FIPS Compliance

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 763 Votes: 0 Revisions: 13

For users that are required to run Orion in FIPS mode:

Devices such as older NETOPIA devices, may be unable to communicate with Orion/NCM.  This due to the fact that these older devices only have SNMPv1 and Telnet/SSH1 protocols available to them.

This issue only arises when running Orion/NCM in FIPS mode, FIPS disables both SNMPv1 and SSHv1 protocols: 

  • All programs that use Network Security Services (NSS) have a FIPS Mode according to the FIPS compliance regulations of US Government.
  • FIPS is not enabled by default with Orion/NCM, this is something that has to be enabled in some restricted environments
  • NETOPIA routers support only SSH1 and/or telnet for command line sessions over tcp/ip.


Note: The issue is likely to occur on any devices that do not support SSH2, not just netopia devices. 

Refer to information about FIPS - What is FIPS 140-2?

Applies to: NCM 7.x

Last modified

Tags

Classifications

Public