Re: [foxboro] Device Relationship Manager

  • From: "Landry, Dwayne" <rdlandry@xxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 14 Sep 2007 08:59:49 -0500

At PPG we are using both DRM and NetSight. I will try and answer the questions 
you have and have included 
For you via BCC with the documents we have from Foxboro on DRM.
DRM basically is a system used to monitor the resources of your I/A system and 
allow TAC to remotely 
Connect to diagnose issues. It also has some alarming features that will 
highlight issues like overloaded CPs,
Low Disk space, Core files, Low Params, OM connections, etc...., etc.... . Data 
can be sent automatically to TAC 
Where they can filter and highlight potential problems and they can notify you 
of the immanent danger.
>
Question: what is DRM going to tell me that I can't already learn from
> other tools like SYSMON, Station detail, or other scripts and tools?
>
Depending on the functionality of your other scripts and tools you may not 
Gain any more information but it will put the information in a box that you 
Don't have to support and probably put your data in a single more accessible 
format.
When you upgrade YOU won't have to rewrite your scripts to work on the new 
system!
>
> Question: will I be able to do packet analysis with DRM? If I have high
> traffic in a node will I be able to tell who it's coming from and what
> it is? Will it resolve MAC addresses into letterbugs and indicate what
> type of traffic I'm looking at?
>
From what I have seen I don't believe you will be able to do packet analysis 
with DRM.
Traffic? No I don't see where the traffic for MESH or Nodebus is available.
We have only had DRM for a short period of time so if someone knows different 
please speak up. 
This box sits on Your second Ethernet network and any data it receives comes 
from scripts running on your AW/WPs.
>
> Question: can DRM actually be used to solve some of the on going
> problems on my system such as:=20
> (1) Station islanding at V6.5.3  =20
> (2) Failure to pass nodebus cable test in node with NCNIs  =20
> (3) Intermittent FCM100 failure and recovery on V8.2 system=20
> (4) Intermittent PIO bus errors on CP60 fieldbus=20
> (5) Apparent network storm on V8.2 system
>
With a remote login from TAC you will be able to use DRM to solve some of your 
Ongoing issues listed above. Connectivity to your Windows boxes is done via an 
app called NetOp which appears to work 
Like PcAnywhere, and Windows Networking. Connectivity to your Unix Boxes is via 
some type of X-Windows, FTP and Telnet.
>
> Question: is DRM mainly focused on CBLAN/nodebus systems? The reason I
> ask is I know there is a product called NetSight from Enterasys that
> allows monitoring of mesh network traffic and switches. Would our
> maintenance dollars be better spent on this product?
DRM covers MESH and CBLAN based systems.

NetSight is a Network monitoring, administration tool for your Enterasys 
network. Our uses of the product include monitoring, diagnostics, firmware 
updates, configuration backup and rollout of our Enterasys switches and have 
basically little to do with Foxboro devices on the network. It gives you a 
window into the realtime architecture of your network showing traffic, 
connectivity, link status, speed, spanning tree, root, backup root, alternate 
paths, etc... DRM and Netsight are two entirely different systems. Netsight 
cannot be used for anything DRM does and Vice Versus. Where would your money be 
better spent? Do you already have a Foxwatch contract? If so then you may be 
already entitled to DRM at no additional cost. As for as Netsight you can do 
most of these functions with SYSMON, Telnet via Serial Cable and Ethernet, 
Internet Explorer, Lan Analyzer.

Hope this helps,
Dwayne Landry
PPG Industries Inc.




 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Kevin Fitzgerrell
Sent: Thursday, September 13, 2007 6:25 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Device Relationship Manager

While I can't contribute any answers here, I'd also be very interested
in hearing from those who are using DRM and/or NetSight.

Regards,

Kevin FitzGerrell

On 9/13/07, dave.caldwell@xxxxxxxxxxxxxx <dave.caldwell@xxxxxxxxxxxxxx> wrote:
> All Knowing List,
>
> I work on a system where Foxwatch hasn't actively been used for years.
> The folks here are a pretty independent bunch, and have been extremely
> successful at troubleshooting system problems with the resources of the
> CSC, the list, TAC, and their own initiative.
>
> Recently, we were offered the Device Relationship Manager (DRM) as part
> of our renewed maintenance agreement.
>
> Question: what is DRM going to tell me that I can't already learn from
> other tools like SYSMON, Station detail, or other scripts and tools?
>
> Question: will I be able to do packet analysis with DRM? If I have high
> traffic in a node will I be able to tell who it's coming from and what
> it is? Will it resolve MAC addresses into letterbugs and indicate what
> type of traffic I'm looking at?
>
> Question: can DRM actually be used to solve some of the on going
> problems on my system such as:=20
> (1) Station islanding at V6.5.3  =20
> (2) Failure to pass nodebus cable test in node with NCNIs  =20
> (3) Intermittent FCM100 failure and recovery on V8.2 system=20
> (4) Intermittent PIO bus errors on CP60 fieldbus=20
> (5) Apparent network storm on V8.2 system
>
> Question: is DRM mainly focused on CBLAN/nodebus systems? The reason I
> ask is I know there is a product called NetSight from Enterasys that
> allows monitoring of mesh network traffic and switches. Would our
> maintenance dollars be better spent on this product?
>
> Looking Forward to Hearing From You,
> Dave
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 



-- No attachments (even text) are allowed --
-- Type: application/msword
-- File: Getting Ready for DRM Network Connectivity_.doc
-- Desc: Getting Ready for DRM Network Connectivity_.doc


-- No attachments (even text) are allowed --
-- Type: application/octet-stream
-- File: Remote%20Services_Whitepaper_Customer.Rev1.1_March-2007.pdf
-- Desc: Remote%20Services_Whitepaper_Customer.Rev1.1_March-2007.pdf


-- No attachments (even text) are allowed --
-- Type: application/msword
-- File: DRM FAQ_Cust.doc
-- Desc: DRM FAQ_Cust.doc


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: