The OCID of the compartment containing the cross-connect group.
The OCID of the cross-connect group this cross-connect belongs to (if any).
A reference name or identifier for the physical fiber connection that this cross-connect uses.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The cross-connect's Oracle ID (OCID).
The cross-connect's current state.
The name of the FastConnect location where this cross-connect is installed.
The FastConnect device that terminates the logical connection. This device might be different than the device that terminates the physical connection.
The FastConnect device that terminates the physical connection.
A string identifying the meet-me room port for this cross-connect.
The port speed for this cross-connect.
Example: {@code 10 Gbps}
The date and time the cross-connect was created, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
For use with Oracle Cloud Infrastructure FastConnect. A cross-connect represents a physical connection between an existing network and Oracle. Customers who are colocated with Oracle in a FastConnect location create and use cross-connects. For more information, see FastConnect Overview.
Oracle recommends you create each cross-connect in a CrossConnectGroup so you can use link aggregation with the connection.
*Note:** If you're a provider who is setting up a physical connection to Oracle so customers can use FastConnect over the connection, be aware that your connection is modeled the same way as a colocated customer's (with {@code CrossConnect} and {@code CrossConnectGroup} objects, and so on).
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized, talk to an administrator. If you're an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/iaas/Content/Identity/Concepts/policygetstarted.htm).