Vlans - Cisco ASR 5000 Series Administration Manual

System Interfaces and Ports
bind interface rp1 source
#end
Step 3 Verify that your static route(s) was configured properly by entering the following command:
context_name
[ ]
Example:
This command produces an output similar to that displayed in the following example that shows a static route to a gateway
with an IP address of 192.168.250.1.
Destination
0.0.0.0/0
0.0.0.0/0
Step 4 Save the configuration as described in the Verifying and Saving Your Configuration chapter.

VLANs

Virtual LANs (VLANs) allow two logically separated networks to use the same physical medium. VLAN
segmentation, also called 802.1q tagging, works by appending a tag identifying the VLAN ID to each Ethernet
frame.
For information on how to create VLANs to handle specific packet types, see the VLANs chapter.
Hypervisors
VLAN usage under KVM is an extension to bridge interface sharing. The difference lies in which interface
participates in the bridge set. The physical interfaces (such as eth0, eth1) are bound to the bridge, which is
used by each guest. These interfaces carry unmodified packets coming externally or being generated internally,
with or without a VLAN ID tag.
VMware supports the use of virtual switches that allow virtual machines on one vSphere host to communicate
with each other using the same protocols as physical switches. The vSwitch emulates a traditional physical
Ethernet network switch by forwarding frames at the data-link layer. A vSphere host can have numerous
virtual switches, each with more than 1,000 internal virtual ports for virtual machines. The vSphere platform
supports the vSphere Standard Switch virtual switch configuration at the host level and the vSphere Distributed
Switch, a single virtual switch that spans multiple associated hosts.
VLANs and Management Ports
The management interface supports VLAN configuration. This support extends to the local context.
Bulkstats can be sent out an interface other than the normal management interface. This interface also supports
VLANs.
You can also configure other OA&M services on separate VLANs.
Yo can assign separate source IP addresses for the OA&M services. OA&M services should not be bound to
the same VLAN as service VLANs. Other services include SGi, Gi, Pi, eGTP or other packet core-specific
interfaces and services.
host_name show ip static-route
#
Nexthop Protocol
192.168.250.1 Static
192.168.250.1 Static
Prec Cost Interface
0 0 MIO1
0 0 rp1 source
ASR 5500 System Administration Guide, StarOS Release 21.4
VLANs
105