Send Netdot-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."


Today's Topics:

   1. Re: Asset Product keeps changing (Carlos Vicente)
   2. Patch Panel to Patch Panel documentation method (Lupe Silva)
   3. Re: Patch Panel to Patch Panel documentation method
      (Carlos Vicente)


----------------------------------------------------------------------

Message: 1
Date: Mon, 21 Apr 2014 17:34:04 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Asset Product keeps changing
To: Justin Miller <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252

Hi Justin,

There is definitely something wrong with how SNMP::Info presents the mikrotik 
information to Netdot. Otherwise, it would not assume that it?s discovering the 
same device. 

I saw some activity on the Microtik class of SNMP::Info recently. I would try 
updating and see if that helps. If not, you?ll have to provide some debugging 
output to try and find the exact issue.

Best,

cv

On Apr 17, 2014, at 4:10 PM, Justin Miller <[email protected]> wrote:

> I've just installed 1.0.6 on wheezy. 
> 
> When I discover the first piece of hardware, the product shows up as 
> "mikrotik x86".  The next piece of hardware that is discovered shows up as 
> "mikrotik RB493AH" which is correct, but the previous device now also has 
> it's product changed to "mikrotik RB493AH". The next one is "mikrotik 
> RB433AH" and all the previous are also changed to this.   Which ever device I 
> discover changes all previous devices to that new product type.
> 
> MikroTik is the manufacture and RB493AH is the product or model.
> 
> Am I doing something wrong, is this a bug, or is this an issue with SNMP:info 
> translations for mikrotik device types?
> 
> Justin
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users




------------------------------

Message: 2
Date: Mon, 21 Apr 2014 15:55:15 -0600
From: Lupe Silva <[email protected]>
Subject: [Netdot-users] Patch Panel to Patch Panel documentation
        method
To: [email protected]
Message-ID:
        <caafpe_zocnegaba5y36sziuaadgedvvcspk6nm2j2bqjmn4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I some of our data closets, we have patch cables that from one patch panel
to another patch panel.  How would I document this patch cable in NetDot?

Lupe Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140421/af61d949/attachment-0001.html
 

------------------------------

Message: 3
Date: Tue, 22 Apr 2014 13:45:43 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Patch Panel to Patch Panel documentation
        method
To: Lupe Silva <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Hi Lupe,

Patch panels and patch cables were not in the original design scope for cable 
plant documentation.

cv

On Apr 21, 2014, at 5:55 PM, Lupe Silva <[email protected]> wrote:

> I some of our data closets, we have patch cables that from one patch panel to 
> another patch panel.  How would I document this patch cable in NetDot?
> 
> Lupe Silva
> 
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users




------------------------------

_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users


End of Netdot-users Digest, Vol 65, Issue 9
*******************************************

Reply via email to