DemandFlow Support Centre

LOGICALCONNECTION: Logical Connection

ReferenceEntity Reference16/04/2026Updated 16/04/2026
Logical or service-level network connection with L2/L3/MPLS configuration, SLA metrics, and endpoint mapping.

LOGICALCONNECTION: Logical Connection

Logical or service-level network connection with L2/L3/MPLS configuration, SLA metrics, and endpoint mapping.

Default definition. This article describes the default LOGICALCONNECTION definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches LOGICALCONNECTION.

Entity properties

PropertyValue
Entity codeLOGICALCONNECTION
Display nameLogical Connection
PluralLogical Connections
Level290

Use cases

LOGICALCONNECTION models network services and logical circuits that ride over physical CONNECTION infrastructure. While CONNECTION tracks individual cables, LOGICALCONNECTION represents the service layer: VLANs, MPLS VPNs, internet transit, SD-WAN overlays, and similar constructs that span multiple physical links. The serviceType field covers the full range of modern network services from simple VLANs through MPLS L3VPN/L2VPN/E-Line, IPSec VPN, GRE tunnels, SD-WAN, LAGs, dark fiber, and wavelength services.

Fields

Service Details

FieldTypeRequiredNotes
nametextYesUnique service identifier
descriptiontext (multi-line)Description
serviceTypeenumYesService Type Valid ids: 1 (VLAN), 2 (VLAN Trunk), 3 (VXLAN), 4 (MPLS L3VPN), 5 (MPLS L2VPN (VPLS)), 6 (MPLS E-Line), 7 (Internet Transit), 8 (Private Peering), 9 (IPSec VPN), 10 (GRE Tunnel), 11 (SD-WAN Overlay), 12 (Link Aggregation (LAG)), 13 (Layer 2 Circuit), 14 (Dark Fiber), 15 (Wavelength Service).
topologyenumYesTopology Valid ids: 1 (Point-to-Point), 2 (Multipoint (Hub & Spoke)), 3 (Any-to-Any (Full Mesh)), 4 (Partial Mesh), 5 (Ring).
statusenumYesStatus Valid ids: 1 (Active), 2 (Planned), 3 (Provisioning), 4 (Failed), 5 (Maintenance), 6 (Decommissioned).

Service Level

FieldTypeRequiredNotes
bandwidthnumberYesBandwidth (Mbps)
cirnumberCommitted Information Rate
qosClassenumQoS Class Valid ids: 1 (Best Effort), 2 (Business), 3 (Premium), 4 (Real-time), 5 (Mission Critical).
slaenumSLA Level Valid ids: 1 (Standard (99.0%)), 2 (Enhanced (99.5%)), 3 (Premium (99.9%)), 4 (Ultra (99.95%)), 5 (Carrier Grade (99.999%)).
redundancyenumRedundancy Valid ids: 1 (None), 2 (Active/Standby), 3 (Active/Active), 4 (N+1), 5 (Geographically Diverse).

Layer 2 Configuration

FieldTypeRequiredNotes
vlanIdtextSingle VLAN or range (e.g., 100 or 100-200)
vninumberVXLAN Network Identifier
dot1qboolean802.1Q Tagged
qinqbooleanQ-in-Q (802.1ad)
outerVlannumberOuter VLAN (S-Tag)
innerVlannumberInner VLAN (C-Tag)
mtunumberMTU Size
jumboFramesbooleanJumbo Frames

Layer 3 Configuration

FieldTypeRequiredNotes
vrftextVRF Name
rdtextRoute Distinguisher
rtImporttextRoute Target Import
rtExporttextRoute Target Export
ipSubnettextCIDR notation (e.g., 10.0.0.0/24)
gatewaytextDefault Gateway
asnnumberAS Number
bgpPeerstext (multi-line)BGP Peers

MPLS Configuration

FieldTypeRequiredNotes
mplsEnabledbooleanMPLS Enabled
lspNametextLabel Switched Path name
labelRangetextLabel Range
trafficEngineeringbooleanTraffic Engineering
fastReroutebooleanFast Reroute
ldpEnabledbooleanLDP Enabled
rsvpEnabledbooleanRSVP-TE Enabled

Service Labels

FieldTypeRequiredNotes
vcIdnumberVC ID (Pseudowire)
pwTypeenumPseudowire Type Valid ids: 1 (Ethernet), 2 (Ethernet VLAN), 3 (PPP), 4 (HDLC), 5 (Frame Relay).
controlWordbooleanControl Word
flowLabelbooleanFlow Label

SLA Metrics

FieldTypeRequiredNotes
latencynumberLatency (ms) Read only.
jitternumberJitter (ms) Read only.
packetLossnumberPacket Loss (%) Read only.
availabilitygaugeAvailability (%) Read only.

Utilization

FieldTypeRequiredNotes
ingressRatenumberIngress Rate (Mbps) Read only.
egressRatenumberEgress Rate (Mbps) Read only.
peakUtilizationgaugePeak Utilization (%) Read only.
averageUtilizationgaugeAverage Utilization (%) Read only.

Service Documentation

FieldTypeRequiredNotes
customerreference → CLIENTCustomer
orderNumbertextOrder Number
circuitIdtextCircuit ID
activationDatedateActivation Date
contractEndDatedateContract End Date
notestext (multi-line)Notes
diagramtext (URL)Network Diagram

Relationships

  • Lookups: customer points at a CLIENT record.
  • Related lists: LOGICALENDPOINT, CONNECTION.

Creating a Logical Connection via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "LOGICALCONNECTION",
  "level":    290,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "serviceType": "1",
  "topology": "1",
  "status": "1"
}

Listing Logical Connections records

# All logical connections in your tenant
GET /v1/entities/LOGICALCONNECTION/SUB

See also

logicalconnectionlogicalconnectionconnectionsentity reference

Was this article helpful?

← Back to Knowledge Base