03.02.2014 Views

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6<br />

<strong>Medianet</strong> Management and Visibility Design Considerations<br />

Network-Embedded Management Functionality<br />

Table 6-1<br />

Summary of Network-Embedded Management Functionality (continued)<br />

Management Product /Tool Management Functionality Description<br />

Simple Network<br />

Management Protocol<br />

(SNMP)<br />

Security management, fault<br />

management, and<br />

performance management<br />

• Telemetry using SNMP can also be used to provide key fault<br />

management information on network infrastructure devices<br />

within a medianet.<br />

• SNMP can be used to collect statistics from network<br />

infrastructure devices for performance management<br />

purposes.<br />

• SNMP traps can be generated for authentication failures to<br />

devices, providing an additional layer of security<br />

management.<br />

AAA services Security management • AAA services can be used to provide centralized access<br />

control for security management, as well as an audit trail<br />

providing visibility into access of network infrastructure<br />

devices.<br />

• For further information regarding network security best<br />

practices, see the <strong>Cisco</strong> SAFE <strong>Reference</strong> <strong>Guide</strong> at the<br />

following URL:<br />

http://www.cisco.com/en/US/docs/solutions/Enterprise/Sec<br />

urity/SAFE_RG/SAFE_rg.html.<br />

NetFlow<br />

NetFlow services provide network administrators access to information regarding IP flows within their<br />

networks. IP flows are unidirectional streams of packets flowing through a network device. They share<br />

common properties such as source address, destination address, protocol, port, DSCP value, and so on.<br />

Network devices, such as switches and routers, can collect and store flow data in the form of flow records<br />

within a NetFlow table or cache. Flow records can then be periodically exported from the NetFlow cache<br />

to one or more NetFlow management collectors located centrally within a data center or campus service<br />

module. NetFlow collectors aggregate exported NetFlow records to provide monitoring and reporting<br />

information regarding the IP traffic flows within the network.<br />

NetFlow provides a means of gaining additional visibility into the various video flows within an<br />

enterprise medianet. From an FCAPS perspective, this visibility can be used for either performance<br />

management purposes or for accounting management purposes. More specifically, NetFlow data can<br />

assist in determining whether sufficient bandwidth has been provisioned across the network<br />

infrastructure to support existing video applications. NetFlow data records can be exported in various<br />

formats depending on the version. The most common formats are versions 1, 5, 7, 8, and 9. NetFlow<br />

export version 9 is the latest version, which has been submitted to the IETF as informational RFC 3954,<br />

providing a model for the IP Flow Information Export (IPFIX) working group within the IETF. NetFlow<br />

version 9 provides a flexible and extensible means of exporting NetFlow data, based on the use of<br />

templates that are sent along with the flow record. Templates contain structural information about the<br />

flow record fields, allowing the NetFlow collector to interpret the flow records even if it does not<br />

understand the semantics of the fields. For more information regarding NetFlow version 9, see the<br />

following URL: http://www.ietf.org/rfc/rfc3954.txt.<br />

OL-22201-01<br />

<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />

6-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!