Scott & list,

 

I wish to clarify my earlier response (I was in a rush when I replied
yesterday).

 

The issue I was trying to describe was not because the SpectroServer
primary NIC IP was not in the device's SNMP access list.

Rather, it was because of routing rules in a private LAN.

 

Here was my SpectroServer lab setup (9.1 H14 on Windows Server 2003):

 

Monitored devices on private LAN:

192.168.18.2

192.168.18.3

192.168.18.4

 

SpectroServer:

NIC 1:   10.17.221.130  (management LAN)

NIC 2:   192.168.18.130 (private LAN)

 

If SS NIC 1 is set as the primary NIC, then the SNMP request for TFTP
dump will originate from SS NIC 2 (192.168.18.130),

but it will direct the device to send the TFTP message to the primary
NIC (NIC 1, 10.17.221.130).

The device needs to be able to route to that address, and in my case, 

since SS NIC 2 is on private LAN, the devices had no idea how to get to
10.17.221.130

 

I figured this out by watching the NCM SNMP communication to the device
IPs on NIC 2 using WireShark.

 

Perhaps there is an NCM config setting I missed (in an RC file?), but in
my haste to solve the issue, I chose to change NIC precedence on the SS
itself since I could do that without penalty.

When I changed the precedence of the SpectroServer NICs so that NIC 2
was primary and NIC 1 was secondary,

the SNMP request for TFTP dump came from SS NIC 2 (192.168.18.130),

AND directed the device to send the TFTP message to the same NIC (NIC 2,
192.168.18.130).

 

HTH,

--Mark S

 

________________________________

Mark Serencha - Inforonics LLC - (m) +1-781-439-0519 - (w)
+1-978-698-7418 -   mark.serencha_AT_inforonics.com
<mailto:[email protected]> 

 

From: Mark Serencha 
Sent: Thursday, January 13, 2011 6:34 PM
To: 'Bourlin, Stephen'; spectrum
Subject: RE: [spectrum] Network Configuration Manager Setup

 

Recently I've discovered that, when using SNMP/TFTP, if the
SpectroServer has more than one NIC, 

the SNMP request may come into the target device from an IP that is not
in the device's SNMP access list.

 

If your SS is multi-homed, running a wireshark and checking the IP's
being used would tell you what's happening right away.

 

HTH,

--Mark S

 

________________________________

Mark Serencha - Inforonics LLC - (m) +1-781-439-0519 - (w)
+1-978-698-7418 -  mark.serencha_AT_inforonics.com
<mailto:[email protected]> 

 

From: Bourlin, Stephen [mailto:[email protected]] 
Sent: Thursday, January 13, 2011 5:50 PM
To: spectrum
Subject: RE:[spectrum] Network Configuration Manager Setup

 

Scott,

 

How are you trying to pull configs? SNMP or Perl, TFTP or FTP? If SNMP
are you using the Read-Write community string? If What type of device
are you pulling the config from? Is the device in front of a firewall or
behind it? Does the device have a NAT'ed address or a regular address? 

 

Regards,

 

Stephen B.

DoIT NMS/NOC

 

NOC Phone # 386-1995

Desk Phone # 733-9154

 

 

From: Casebere, Scott [mailto:[email protected]] 
Sent: Thursday, January 13, 2011 11:57 AM
To: spectrum
Subject: [spectrum] Network Configuration Manager Setup

 

Has anyone ever seen a document on setting up the Configuration Manger
to pull configs? Whenever I try to "Capture Config" I get an error
stating I need to check the community string; everything is setup right
though. I also see the NCMservice running on the server. 

 

Thanks,

Scott Casebere

PRC NOC

Noc TierII Engineer

500 North Central Expressway

Suite 266
Plano, TX 75074

M 972.955.1542

O 954.838.4109

 

*       --To unsubscribe from spectrum, send email to [email protected]
with the body: unsubscribe spectrum [email protected] 

*       --To unsubscribe from spectrum, send email to [email protected]
with the body: unsubscribe spectrum [email protected] 


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to