20.07.2014 Views

JetNet Series Industrial L2 / L3 Rackmount / Rail Ethernet Switch

JetNet Series Industrial L2 / L3 Rackmount / Rail Ethernet Switch

JetNet Series Industrial L2 / L3 Rackmount / Rail Ethernet Switch

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.

<strong>Industrial</strong> <strong>L2</strong> / <strong>L3</strong> <strong>Rackmount</strong> / <strong>Rail</strong> <strong>Ethernet</strong> <strong>Switch</strong><br />

Independent Ring Operation<br />

Unlike traditional redundancy technologies, such<br />

as RSTP, which takes all LAN devices as a single<br />

system, each of Korenix redundant rings operates<br />

independently. The influence of any network failure<br />

is limited within the ring itself and will not spread to the<br />

other parts, as a result ensuring network scalability and<br />

high quality data transmission.<br />

<strong>Industrial</strong><br />

Intelligent<br />

NMS<br />

<strong>Rackmount</strong><br />

PoE Plus<br />

<strong>Switch</strong><br />

<strong>Industrial</strong><br />

PoE Plus<br />

<strong>Switch</strong><br />

<strong>Industrial</strong><br />

12-24V<br />

PoE <strong>Switch</strong><br />

<strong>Industrial</strong><br />

PoE <strong>Switch</strong><br />

One RSTP Network<br />

Ring 1 Ring 2 Ring 3<br />

<strong>Rackmount</strong><br />

<strong>L3</strong>/<strong>L2</strong> <strong>Switch</strong><br />

Gigabit<br />

Managed<br />

<strong>Switch</strong><br />

IEEE 802.1s Multiple Spanning Tree Protocol<br />

The <strong>JetNet</strong> series support IEEE 802.1s Multiple Example: Instance 1 represents VLAN 20. Instance 2<br />

Spanning Tree Protocol (MSTP). The switch with represents VLAN 10.<br />

enabled MSTP can select the root switch for each In instance 1, there is one root and one blocking path.<br />

instance, and block and form the forwarding path for The VLAN 20 data can be transmitted from switch 3 to 1,<br />

each instance. Each instance represents one VLAN. It is and then to 2 or vise versa.<br />

the limitation in STP/RSTP as the 2 traditional protocols In instance 2, there is another root and another blocking<br />

can only block one path for all the existing VLANs in the path. The VLAN 10 data can be transmitted from switch<br />

same environment.<br />

3 to 2, then to 1 or vise versa.<br />

Managed<br />

<strong>Ethernet</strong><br />

<strong>Switch</strong><br />

Entry-level<br />

<strong>Switch</strong><br />

Wireless<br />

Outdoor AP<br />

Embedded<br />

PoE/Router<br />

Computer<br />

(LINUX)<br />

<strong>Industrial</strong><br />

Communication<br />

Computer<br />

(WIN/LINUX)<br />

<strong>Ethernet</strong>/PoE/<br />

Serial Board<br />

<strong>JetNet</strong> 5428G<br />

3<br />

<strong>Ethernet</strong><br />

I/O Server<br />

Instance 1 – VLAN 20<br />

Blocking<br />

2<br />

3<br />

1<br />

Instance 2 – VLAN 10<br />

Blocking<br />

Instance 1 – VLAN 20<br />

Forwarding Paths<br />

Root<br />

2 1<br />

3<br />

Media<br />

Converter<br />

Serial Device<br />

Server<br />

Instance 2 – VLAN 10<br />

Root <strong>Switch</strong><br />

Instance 1 – VLAN 20<br />

Root <strong>Switch</strong><br />

Instance 2 – VLAN 10<br />

Forwarding Paths<br />

Root<br />

2 1<br />

SFP Module<br />

Din <strong>Rail</strong><br />

Power Supply<br />

A Beijer Electronics Group Company<br />

www.korenix.com<br />

150

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

Saved successfully!

Ooh no, something went wrong!