Page History
...
| Note |
|---|
When a VLAN Logical Interface is first created, it will be disabled by default. |
SBC SWe
...
Edge
VLAN sub-interfaces allow the separation of either management traffic between the service provider and the customer, or to keep media traffic from multiple sources separate (that need to exist on the same SWe Lite Edge instance). For example, a service provider could use a VLAN to manage a SWe Lite Edge at a customer premise, while also having a management interface for the customer; the service provider and the customer would be on the same physical network, but have separate logical interfaces.
...
For configuring VLAN sub-interfaces, refer to Managing VLANs - SBC SWe Lite.Edge
About Logical Interfaces - IPv4 and IPv6 Support
...
In this example, the LAN uses IPv6, and the WAN uses IPv4. The
| Spacevars | ||
|---|---|---|
|
...
| borderStyle | none |
|---|
...
...
IPv6 to IPv6 - Example
In this example, both the LAN and the WAN use IPv6. The SBC is responsible for serving as a back-to-back user agent between the two call legs. The DNS server and NTP server are both on the WAN.
...
| borderStyle | none |
|---|
...
...
IPv4 to IPv6 - Example
In this example, the LAN uses IPv4 and the WAN uses IPv6. Just as in the IPv6-to-IPv4 case, the SBC is responsible for protocol interworking between the two call legs. The DNS server and the NTP server are both on the LAN.
...
| borderStyle | none |
|---|
...
Managing Logical Interfaces
| Excerpt | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To view an interface's properties:
...
If the logical interface is part of a redundant Ethernet pair, several of the options on the secondary logical interface will become read-only.
pagebreak
Overview
Content Tools