cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

License Devices for Network componet

Jump to solution

Should I need to license network device to collect their performance? If they're not licensed, any affect on building application stack process?

Thank you.

0 Kudos
1 Solution

Discovery and licensing of network devices will provide visibility into inventory detail (model information, software version, feature set, etc) as well as device performance (packet loss, memory and CPU utilization) however licensing network devices will not provide any application dependency detail (TCP connections). TCP connections are only collected from the server/desktop OS (Windows, Linux, AIX) You would typically license network devices for asset management and for identifying performance issues.

The platform monitors TCP connections (Netstat) from the OS on 5 minute intervals during Performance. (Only inventory data is collected during Discovery) A device must be licensed for performance collection to occur which includes Netstat collection. The user then has the option to manually build application stacks or use the automated 'build app stacks'. Below is a link that will detail the automated process:

https://docs.flexera.com/foundationcloudscape/help/FCUsingPlatform_BuildStacks.htm?Highlight=build

Servers that are discovered after 'build app stacks' is run can be manually added to an existing/created stack or the user can rerun 'build app stacks' to have the platform group the device automatically. Please note that build app stacks feature will not place devices into custom groups nor will the build app stacks feature attempt to group devices that are in a saved or confirmed stack. 

 

 

View solution in original post

3 Replies
RCharette
Level 9 Flexeran
Level 9 Flexeran

Licensing network devices (routers, switches, firewalls, etc) will cause the platform to monitor device performance such as CPU, Memory, interface utilization and interface loss (discards/errors) Please note that application dependency (TCP connections) are only collected from the OS (Windows/Linux/AIX)

Not licensing the network devices will have no negative affect on capturing TCP connections from the OS nor building application stacks.

0 Kudos

Hello @RCharette 

I thought the data from the network device would help determine the connection server-to-server and stack-to-stack. If not, what will those data be used for, do I need to collect them?

Why is the application mapped only after the performance monitoring step? How is mapping process and what data does it need?

In case we collect more servers after building the application stacks, could these servers be added to the availability stacks if I select Build App Stacks again?

Could you help me explain more?

Thank you

0 Kudos

Discovery and licensing of network devices will provide visibility into inventory detail (model information, software version, feature set, etc) as well as device performance (packet loss, memory and CPU utilization) however licensing network devices will not provide any application dependency detail (TCP connections). TCP connections are only collected from the server/desktop OS (Windows, Linux, AIX) You would typically license network devices for asset management and for identifying performance issues.

The platform monitors TCP connections (Netstat) from the OS on 5 minute intervals during Performance. (Only inventory data is collected during Discovery) A device must be licensed for performance collection to occur which includes Netstat collection. The user then has the option to manually build application stacks or use the automated 'build app stacks'. Below is a link that will detail the automated process:

https://docs.flexera.com/foundationcloudscape/help/FCUsingPlatform_BuildStacks.htm?Highlight=build

Servers that are discovered after 'build app stacks' is run can be manually added to an existing/created stack or the user can rerun 'build app stacks' to have the platform group the device automatically. Please note that build app stacks feature will not place devices into custom groups nor will the build app stacks feature attempt to group devices that are in a saved or confirmed stack.