0% found this document useful (0 votes)
16 views6 pages

JNCIS - SWITCH - 2 - Virtual Networks

The document provides an overview of configuring virtual networks in Junos, focusing on port types such as access and trunk ports, and the default VLAN. It details the creation of VLANs, assignment of ports, and the configuration of voice VLANs for differentiating data and voice traffic. Additionally, it explains the concept of Routed VLAN Interfaces (RVI) for inter-VLAN routing and the importance of associating RVIs with VLANs for operational status.

Uploaded by

Marcin Krajnik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views6 pages

JNCIS - SWITCH - 2 - Virtual Networks

The document provides an overview of configuring virtual networks in Junos, focusing on port types such as access and trunk ports, and the default VLAN. It details the creation of VLANs, assignment of ports, and the configuration of voice VLANs for differentiating data and voice traffic. Additionally, it explains the concept of Routed VLAN Interfaces (RVI) for inter-VLAN routing and the importance of associating RVIs with VLANs for operational status.

Uploaded by

Marcin Krajnik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

VIRTUAL NETWORKS

PORTS IN JUNOS

 General port types in Junos


o Access ports
 By default all ports on an EX series switches are configured as access ports
 associated with the default VLAN (untagged VLAN)
o Trunk ports
 can carry tagged and untagged traffic (when configured with native-vlan-id statement)

DEFAULT VLAN

 All switch ports not specifically assigned to a user-defined VLAN belong to default VLAN

o Default VLAN does not use 802.1Q tag


 802.1Q tag can be manually assigned to the default VLAN

{master:0}[edit]
root# set vlans default vlan-id 100

{master:0}
root> show vlans
Name Tag Interfaces
default 100
ge-0/0/0.0, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0,
ge-0/0/4.0, ge-0/0/5.0, ge-0/0/6.0*, ge-0/0/7.0*,
ge-0/0/8.0*, ge-0/0/9.0*, ge-0/0/10.0*, ge-0/0/11.0*,
ge-0/0/12.0*, ge-0/0/13.0*, ge-0/0/14.0*, ge-0/0/15.0*,
ge-0/0/16.0, ge-0/0/17.0, ge-0/0/18.0, ge-0/0/19.0,
ge-0/0/20.0, ge-0/0/21.0, ge-0/0/22.0, ge-0/0/23.0,
xe-0/1/0.0

CREATING VLANS AND ASSIGNING PORTS

 creating VLANs:

[edit]
set vlans v10 vlan-id 10
set vlans v20 vlan-id 20

{master:0}[edit]
user@Switch-1# show vlans
v10 {
vlan-id 10;
}
v20 {
vlan-id 20;
}

 additional options are available


{master:0}[edit]
user@Switch-1# set vlans v10 ?
Possible completions:
<[Enter]> Execute this command
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
description Text description of the VLAN
> dot1q-tunneling Dot1q-tunneling parameters
> filter Packet filtering
> interface Name of interface that uses this VLAN
l3-interface Layer 3 interface for this VLAN
mac-limit Number of MAC addresses allowed on this VLAN (1..65535)
mac-table-aging-time MAC aging time (60..1000000 seconds)
no-local-switching Disable local switching
no-mac-learning Disable mac learning
primary-vlan Primary VLAN for this community VLAN
vlan-id 802.1q tag (1..4094)
vlan-range VLAN range in the form '<vlan-id-low>-<vlan-id-high>'
| Pipe through a command

 Configuring access ports

[edit]
set interfaces ge-0/0/6 unit 0 family ethernet-switching port-mode access
set interfaces ge-0/0/6 unit 0 family ethernet-switching vlan members v10

{maste:0}[edit]
user@Switch-1# show interfaces ge-0/0/6
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members v10;
}
}
Same task accomplished.
}
Configuration should be
done in one place to
 The same configuration (assigning port to VLAN) can be accomplished under [edit vlans]:
preserve consistency.
{master:0}[edit vlans]
user@Switch-1# show
v10 {
vlan-id 10;
interface {
ge-0/0/8.0;
}
}
v20 {
vlan-id 20;
interface {
ge-0/0/9.0;
}
}

CONFIGURING TRUNK PORTS

 Configuring trunk ports:

set interfaces ge-0/0/7 unit 0 family ethernet-switching port-mode trunk


set interfaces ge-0/0/7 unit 0 family ethernet-switching vlan members [ v10 v20 ]

{master:0}[edit]
user@Switch-1# show interfaces ge-0/0/7
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ v10 v20 ];
}
}
}

 allowing all configured vlans on trunk ports

set interfaces ge-0/0/7 unit 0 family ethernet-switching vlan members all

{master:0}[edit interfaces ge-0/0/12]


user@Switch-1# show
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
}
}

 this can be achieved also under [edit vlans]

{master:0}[edit vlans]
user@Switch-1# show
v10 {
vlan-id 10;
interface {
ge-0/0/12.0;
}
}
v20 {
vlan-id 20;
interface {
ge-0/0/12.0;
}
}

VERIFYING VLAN ASSIGNMENT


VOICE VLAN

 access port accepts both tagged (voice) and untagged (data) frames

 used with CoS to differentiate data and voice traffic


 Voice VLAN and CoS values can be communicated to IP phones through Link Layer Discovery Protocol (LLDP-MED)

[edit ethernet-switching-options]
show
voip {
interface (access-ports | interface-name) {
vlan (vlan-name | vid);
forwarding-class CLASS;
}
}

[edit ethernet-switching-options]
show
voip {
interface ge-0/0/6.0 {
vlan voice;
forwarding-class assured-forwarding;
}
}

[edit]
show
interfaces ge-0/0/6 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members data;
}
}
}
}

[edit]
show
interfaces ge-0/0/12 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ data voice ];
}
}
}
}
MONITORING VOICE VLAN

TRUNK PORTS VS UNTAGGED TRAFFIC

 Trunk ports only send tagged traffic by default. If there is a need to forward also untagged traffic: native-vlan-id

[edit interfaces]
show ge-0/0/12
unit 0 {
family ethernet-switching {
port-mode trunk;
vlans {
members [ v14 v15 ];
}
native-vlan-id default;
}
}
RVI – ROUTED VLAN INTERFACE

 routed VLAN interface (RVI) is a logical L3 interface defined that facilitates inter-VLAN routing

[edit]
show interfaces vlan
unit 14 {
family inet {
address 172.23.14.1/24;
}
}
unit 15 {
family inet {
address 172.23.15.1/24;
}
}
unit 16 {
family inet {
address 172.23.16.1/24;
}
}

 Associating RVIs with VLANs

[edit]
show vlans
v14 {
vlan-id 14;
interface {
ge-0/0/6.0;
ge-0/0/7.0;
}
l3-interface vlan.14; < RVI is associated with vlan
}
v15 {
vlan-id 15;
interface {
ge-0/0/8.0;
ge-0/0/9.0;
}
l3-interface vlan.15; < RVI is associated with vlan
}
v16 {
vlan-id 16;
interface {
ge-0/0/10.0;
ge-0/0/11.0;
}
l3-interface vlan.16; < RVI is associated with vlan
}

 Verifying Interface state


o show interface terse vlan

 RVI must be associated with a VLAN and that VLAN must have at least one operational Layer 2 interface before the RVI becomes
operational

You might also like