<div>
What device on your network routes traffic between VLAN's? &nbsp;Does it know about VLAN 25 and can it ping 172.16.25.251?
</div>


<div>
I found the solution doing more research.
</div>


<div>
<div class="content wysiwyg-content">
I have a server that I would like to make my netflow collection server. &nbsp;I am trying to setup my 6509 to send netflow traffic from a specific vlan to the collection server. &nbsp;Here is what I have so far, the parts of my cfg that are relevant :<br />
<br />
int vlan25<br />
&nbsp;ip address 172.16.25.251 255.255.255.0<br />
&nbsp;ip route-cache flow<br />
no mls acl tcam share-global<br />
mls netflow interface<br />
mls flow ip interface-full<br />
no mls flow ipv6<br />
mls nde sender version 5<br />
mls cef error action freeze<br />
mls nde sender version 5<br />
ip flow ingress layer2-switched vlan 25<br />
ip flow export layer2-switched vlan 25<br />
ip flow-export destination SERVERIPINDIFFERENTNETWORK<wbr /> 9996<br />
<br />
Very strange, I cannot seem to ping 172.16.25.251 from anywhere. &nbsp;Which I assume is my bigger issue, but then:<br />
<br />
&nbsp;Total Netflow Data Export Packets are:<br />
&nbsp; &nbsp; 0 packets, 0 no packets, 0 records<br />

</div>
</div>


I have a server that I would like to make my netflow collection server.  I am trying to setup my 6509 to send netflow traffic from a specific vlan to the collection server.  Here is what I have so far, the parts of my cfg that are relevant :

int vlan25
 ip address 172.16.25.251 255.255.255.0
 ip route-cache flow
no mls acl tcam share-global
mls netflow interface
mls flow ip interface-full
no mls flow ipv6
mls nde sender version 5
mls cef error action freeze
mls nde sender version 5
ip flow ingress layer2-switched vlan 25
ip flow export layer2-switched vlan 25
ip flow-export destination SERVERIPINDIFFERENTNETWORK 9996

Very strange, I cannot seem to ping 172.16.25.251 from anywhere.  Which I assume is my bigger issue, but then:

 Total Netflow Data Export Packets are:
    0 packets, 0 no packets, 0 records


What device on your network routes traffic between VLAN&amp;#39;s?  Does it know about VLAN 25 and can it ping 172.16.25.251?

I found the solution doing more research.

Netflow and Cisco 6509

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.