Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

SNTC & NOS collector

Hi,

Does SNTC & NOS share or can share the same collector and how does a NOS engagement adds to the data & information already collected?

1 ACCEPTED SOLUTION

Accepted Solutions

HiWe do have customers that

Hi

We do have customers that have both SNTC & NOS and share a single collector, but not all collector configurations are supported, especially since NOS deployments are very customizable in terms of the services they deliver.  It usually requires the NOS team (which deploy and maintain their collector) and the SNTC deployment team to assess the situation and make a determination.  

 

In terms of what NOS adds to the data & information already collected by SNTC, NOS is a much different service than SNTC because it is high-touch with Cisco NCE assigned to the account.  Focus is around Optimization.  There is core NOS (route switch) and then tons of options (data center, security, wireless, Collab, etc.).  Some of the deliverables overlap (specifically the alerts-eox, fn, psirt), but the approach in NOS is different.  There is more of a consulting approach it it.  For example, EOX is about 5 year roadmap plan for what is coming EOL in next 5 years and lifecycle planning.  PSIRT includes more detailed recommendation consulting on what to do to address the impacts to the customer.  Beyond alerts, some of the common automation-enabled deliverables include Configuration Best Practice Analysis, Customer-Specific configuration compliance analysis, Syslog analysis, SW Compliance reporting/tracking, unidentified inventory reporting, topology diagramming, Network Improvement Plan, and Network Audits.

 

1 REPLY

HiWe do have customers that

Hi

We do have customers that have both SNTC & NOS and share a single collector, but not all collector configurations are supported, especially since NOS deployments are very customizable in terms of the services they deliver.  It usually requires the NOS team (which deploy and maintain their collector) and the SNTC deployment team to assess the situation and make a determination.  

 

In terms of what NOS adds to the data & information already collected by SNTC, NOS is a much different service than SNTC because it is high-touch with Cisco NCE assigned to the account.  Focus is around Optimization.  There is core NOS (route switch) and then tons of options (data center, security, wireless, Collab, etc.).  Some of the deliverables overlap (specifically the alerts-eox, fn, psirt), but the approach in NOS is different.  There is more of a consulting approach it it.  For example, EOX is about 5 year roadmap plan for what is coming EOL in next 5 years and lifecycle planning.  PSIRT includes more detailed recommendation consulting on what to do to address the impacts to the customer.  Beyond alerts, some of the common automation-enabled deliverables include Configuration Best Practice Analysis, Customer-Specific configuration compliance analysis, Syslog analysis, SW Compliance reporting/tracking, unidentified inventory reporting, topology diagramming, Network Improvement Plan, and Network Audits.

 

336
Views
0
Helpful
1
Replies
CreatePlease to create content