TNETX15VE datasheet(47/113 Pages) TI1

47 / 113 page

TNETX15VE

VLAN-ENGINE ADDRESS-LOOKUP DEVICE

SPWS028B – APRIL 1997 – REVISED SEPTEMBER 1997

POST OFFICE BOX 655303

• DALLAS, TEXAS 75265

monitor registers

In addition to the NMON monitoring provided by the TNETX3150/TNETX3150A, using the TNETX15VE adds

software-configurable modes of monitoring traffic, which are described as follows.

Address monitoring: Unicast traffic is sent to a second port regardless of VLAN by modifying the table entry

in the TNETX15VE SRAM memory using the edit function on the ADD command. If the

table entry is modified to set the CUPLINK bit, any packet destined for that address is

queued for transmit on the port specified by uplinkport. Multicast addresses do not

have such a bit in their entry, but multicast addresses can include any port as a

monitoring port by changing the portflag vector to include a new port that is subject to

that vector being ANDed with that port’s VLANmask register. Both of these modes

require an external host to perform the modification to the address table value. Multiple

addresses can be monitored at the same time. Both sides of a suspect transaction are

monitored by setting the CUPLINK bit for both destination addresses that are

monitored. All the traffic going to the destination addresses (so marked) is forwarded to

the port specified in the uplinkport register.

Port monitoring:

All traffic to or from a specified port is copied to another port of choice. The port to be

sampled is specified in the mirror port-select register; the output goes to the port

selected in the uplinkport register, and the activity is gated on and off by setting the

MIRR bit in the control register (0x8, 0x9). The traffic includes packets that would not

normally be routed through the TNETX3150/TNETX3150A (when both the source and

destination addresses are on the same port, the inbound packet is normally dropped).

However, a second copy of the packet is not generated if not necessary. For example, a

packet inbound on the uplinkport (destined for the mirrorport) is not copied back to the

uplinkport because it has already been seen there.

Both port and address monitoring can be active at the same time, but only one destination port is used at one

time; both monitoring modes direct traffic to the port specified in the uplinkport register (be careful in setting up

extensive monitoring). If the streams being monitored are running in full-duplex mode, it is possible to queue

more traffic per second to the monitoring port than can be transmitted there. When the transmit queue at the

output port fills up, packets are dropped.

uplink routing register, uplinkport at 0xF0 (DIO)

BIT

Reserved

Uplink

Initial Values After Reset

The uplinkport register contents are used in both port monitoring and address monitoring to specify the output

port for the data being monitored. The 4-bit field uplink specifies the destination port number for monitored

frames. The Uplink field is read/write. Changing uplink changes the port that subsequent packets are queued

to. Changing uplink does not move frames queued to the previous port value.

TNETX15VE 数据表(PDF) 47 Page - Texas Instruments

TNETX15VE 数据表(HTML) 47 Page - Texas Instruments

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

数据表下载