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

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
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-devel digest..."


Today's Topics:

   1. [Netdot - Feature #1677] (New) HTTP Discover for  non-SNMP
      devices ([email protected])
   2. [Netdot - Bug #1678] (New) Latest OS warning false        positive
      in Model/OS report ([email protected])
   3. [Netdot - Bug #1679] (New) module inserted in     transceiver
      port container is not bound to asset ([email protected])
   4. [Netdot - Bug #1680] (New) netdot does not recognice      Juniper
      MX80 ([email protected])


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

Message: 1
Date: Sun, 19 Aug 2012 20:32:43 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1677] (New) HTTP Discover
        for     non-SNMP devices
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1677 has been reported by Nicolas Mathey.

----------------------------------------
Feature #1677: HTTP Discover for non-SNMP devices
https://osl.uoregon.edu/redmine/issues/1677

Author: Nicolas Mathey
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: 


Would be usefull to develop HTTP Discovery process in order to retrieve 
information from non-SNMP devices like Cisco IPPhones (i.e. S/N, Model, 
Firmware version,contact number, etc.).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


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

Message: 2
Date: Mon, 20 Aug 2012 01:08:37 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1678] (New) Latest OS warning
        false   positive in Model/OS report
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1678 has been reported by James Andrewartha.

----------------------------------------
Bug #1678: Latest OS warning false positive in Model/OS report
https://osl.uoregon.edu/redmine/issues/1678

Author: James Andrewartha
Status: New
Priority: Low
Assignee: 
Category: 
Target version: 
Resolution: 


htdocs/report/device_inventory.html line 223 should be
if ( $product->latest_os && ($os ne $product->latest_os) ){
as $latest_os is the string "(recommended: ".$product->latest_os.")", not the 
product latest OS.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


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

Message: 3
Date: Mon, 20 Aug 2012 04:05:47 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1679] (New) module inserted in
        transceiver port container is not bound to asset
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1679 has been reported by Erik Wenzel.

----------------------------------------
Bug #1679: module inserted in transceiver port container is not bound to asset
https://osl.uoregon.edu/redmine/issues/1679

Author: Erik Wenzel
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: 


My test scenario is a cisco catalyst 6509 with a WS-X6724-SFP in Slot 1. After 
connecting a transceiver module to a transceiver port container a known asset 
with a serial number is still "installed = "no" in 
[Reports]->[Asset]->by"Detailed". Module insertion verified at 
[Management]->[Devices]->[test-router-6500]->[Modules]. Serial number in 
available under SNMPv2-SMI::mib-2.47.1.1.1.1.11.*. The serial number is not 
checked for availability in asset database table. This means that you can't 
move FRU from one device to another without losing track of that asset. Asset 
management is broken.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


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

Message: 4
Date: Mon, 20 Aug 2012 06:38:04 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1680] (New) netdot does not
        recognice       Juniper MX80
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1680 has been reported by Erik Wenzel.

----------------------------------------
Bug #1680: netdot does not recognice Juniper MX80
https://osl.uoregon.edu/redmine/issues/1680

Author: Erik Wenzel
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: 


Netdisco mibs know about MX80 Chassis:
<pre>
# grep -i mx80 /usr/share/netdisco/mibs/juniper/mib-jnx-chas-defines.txt
- MX80
  jnxProductLineMX80      OBJECT IDENTIFIER ::= { jnxProductLine      57 }
  jnxProductNameMX80      OBJECT IDENTIFIER ::= { jnxProductName      57 }
  jnxProductModelMX80     OBJECT IDENTIFIER ::= { jnxProductModel     57 }
  jnxProductVariationMX80 OBJECT IDENTIFIER ::= { jnxProductVariation 57 }
    jnxProductMX80        OBJECT IDENTIFIER ::= { jnxProductVariationMX80 1 }
    jnxProductMX80-48T    OBJECT IDENTIFIER ::= { jnxProductVariationMX80 2 }
    jnxProductMX80-T      OBJECT IDENTIFIER ::= { jnxProductVariationMX80 3 }
  jnxChassisMX80          OBJECT IDENTIFIER ::= { jnxChassis          57 }
  jnxSlotMX80             OBJECT IDENTIFIER ::= { jnxSlot     57 }
    jnxMX80SlotFPC        OBJECT IDENTIFIER ::= { jnxSlotMX80 1  }
    jnxMX80SlotCFEB       OBJECT IDENTIFIER ::= { jnxSlotMX80 2  }
    jnxMX80SlotRE         OBJECT IDENTIFIER ::= { jnxSlotMX80 3  }
    jnxMX80SlotPower      OBJECT IDENTIFIER ::= { jnxSlotMX80 4  }
    jnxMX80SlotFan        OBJECT IDENTIFIER ::= { jnxSlotMX80 5  }
  jnxMediaCardSpaceMX80      OBJECT IDENTIFIER ::= { jnxMediaCardSpace    57 }
    jnxMX80MediaCardSpacePIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceMX80 1 }
    jnxMX80MediaCardSpaceMIC OBJECT IDENTIFIER ::= { jnxMediaCardSpaceMX80 2 }
  jnxMidplaneMX80         OBJECT IDENTIFIER ::= { jnxBackplane        57 }
  jnxModuleMX80           OBJECT IDENTIFIER ::= { jnxModule     57 }
    jnxMX80FPC            OBJECT IDENTIFIER ::= { jnxModuleMX80 1  }
    jnxMX80CFEB           OBJECT IDENTIFIER ::= { jnxModuleMX80 2  }
    jnxMX80RE             OBJECT IDENTIFIER ::= { jnxModuleMX80 3  }
    jnxMX80Power          OBJECT IDENTIFIER ::= { jnxModuleMX80 4  }
    jnxMX80PowerAC        OBJECT IDENTIFIER ::= { jnxModuleMX80 5  }
    jnxMX80Fan            OBJECT IDENTIFIER ::= { jnxModuleMX80 6  }

$ dpkg -l netdisco-mibs-installer
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                     Version                  Description
+++-========================-========================-================================================================
ii  netdisco-mibs-installer  1.7                      Netdisco MIB bundle 
installer package
</pre>

Netdot shows a MX80 Chassis asset as "Juniper Networks .57". Which is 
undescriptive. Show chassis as "Juniper Networks MX80".


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


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

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


End of Netdot-devel Digest, Vol 65, Issue 16
********************************************

Reply via email to