18.11.2014 Views

Clavister cOS Core Administration Guide

Clavister cOS Core Administration Guide

Clavister cOS Core Administration Guide

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 4: Routing<br />

Implementing BPDU Relaying<br />

The <strong>cOS</strong> <strong>Core</strong> BDPU relaying implementation only carries STP messages. These STP messages can<br />

be of three types:<br />

• Normal Spanning Tree Protocol (STP)<br />

• Rapid Spanning Tree Protocol (RSTP)<br />

• Multiple Spanning Tree Protocol (MSTP)<br />

• Cisco proprietary PVST+ Protocol (Per VLAN Spanning Tree Plus)<br />

<strong>cOS</strong> <strong>Core</strong> checks the contents of BDPU messages to make sure the content type is supported. If it<br />

is not, the frame is dropped.<br />

Enabling/Disabling BPDU Relaying<br />

BPDU relaying is disabled by default and can be controlled through the advanced setting Relay<br />

Spanning-tree BPDUs. Logging of BPDU messages can also be controlled through this setting.<br />

When enabled, all incoming STP, RSTP and MSTP BPDU messages are relayed to all transparent<br />

interfaces in the same routing table, except the incoming interface.<br />

4.8.5. MPLS Pass Through<br />

Multi-protocol Label Switching (MPLS) is a standard that allows the attaching of labels to IP<br />

packets to provide information about the packet's eventual destination. The router that initially<br />

attached the MPLS label is known as the ingress router.<br />

Network nodes that support MPLS can then use this attached information to route packets<br />

without needing to perform route lookups and therefore increase processing speed. In addition<br />

to overall faster traffic movement, MPLS also makes it easier to manage Quality of Service (QoS).<br />

MPLS is considered to be "multi-protocol" because it works with the Internet Protocol,<br />

Asynchronous Transport Mode (ATM) and frame relay network. When considered in reference to<br />

the OSI network model, MPLS allows packets to be forwarded at the layer two level rather than at<br />

the layer three level and for this reason it is said to operate at the two and a half level.<br />

<strong>cOS</strong> <strong>Core</strong> MPLS Support<br />

<strong>cOS</strong> <strong>Core</strong> supports MPLS Pass Through. This is relevant in transparent mode scenarios where the<br />

MPLS labelled packets are allowed to traverse the <strong>Clavister</strong> Security Gateway. <strong>cOS</strong> <strong>Core</strong> can<br />

optionally validate the integrity of these MPLS packets and the administrator can change the<br />

advanced setting Relay MPLS to specify the specific action to be taken. The possible values for<br />

this setting are:<br />

• Ignore - Verify packets and allow all verified MPLS labelled packets to pass silently. Packets<br />

that fail verification are logged.<br />

• Log - Verify packets and allow all verified MPLS packets to pass as well as being logged.<br />

Packets that fail verification are also logged.<br />

• Drop - Silently drop all MPLS packets without verification or logging.<br />

• Drop/Log - Drop all MPLS packets without verification and log these drops.<br />

330

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

Saved successfully!

Ooh no, something went wrong!