57 SVP_R_BULK_REQ = 0x07,
58 SVP_R_BULK_ACK = 0x08,
59 SVP_R_LOG_REQ = 0x09,
60 SVP_R_LOG_ACK = 0x0A,
61 SVP_R_LOG_RM = 0x0B,
62 SVP_R_LOG_RM_ACK = 0x0C,
63 SVP_R_SHOOTDOWN = 0x0D,
64 SVP_R_ROUTE_REQ = 0x0E,
65 SVP_R_ROUTE_ACK = 0x0F
66 } svp_op_t;
67
68 typedef enum svp_status {
69 SVP_S_OK = 0x00, /* Everything OK */
70 SVP_S_FATAL = 0x01, /* Fatal error, close connection */
71 SVP_S_NOTFOUND = 0x02, /* Entry not found */
72 SVP_S_BADL3TYPE = 0x03, /* Unknown svp_vl3_type_t */
73 SVP_S_BADBULK = 0x04 /* Unknown svp_bulk_type_t */
74 } svp_status_t;
75
76 /*
77 * A client issues the SVP_R_VL2_REQ whenever it needs to perform a VLS->UL3
78 * lookup. Requests have the following structure:
79 */
80 typedef struct svp_vl2_req {
81 uint8_t sl2r_mac[ETHERADDRL];
82 uint8_t sl2r_pad[2];
83 uint32_t sl2r_vnetid;
84 } svp_vl2_req_t;
85
86 /*
87 * This is the message a server uses to reply to the SVP_R_VL2_REQ. If the
88 * destination on the underlay is an IPv4 address, it should be encoded as an
89 * IPv4-mapped IPv6 address.
90 */
91 typedef struct svp_vl2_ack {
92 uint16_t sl2a_status;
93 uint16_t sl2a_port;
94 uint8_t sl2a_addr[16];
95 } svp_vl2_ack_t;
96
97
236 /*
237 * A route-request (SVP_R_ROUTE_REQ) queries the local SVP server to get a
238 * far-remote (i.e. another Triton Data Center, nee. SDC) SVP server for
239 * far-remote networks. Modern overlay modules will request IP destinations
240 * for remote-Triton networks, but they must know how to reach the
241 * remote-Triton SVP server.
242 */
243 typedef struct svp_route_req {
244 uint32_t srr_vnetid; /* Requester's vnet ID. */
245 uint16_t srr_vlan; /* Requester's VLAN ID. */
246 uint16_t srr_pad; /* Zero on xmit, ignore on receipt. */
247 uint8_t srr_srcip[16]; /* VL3 Source IP. */
248 uint8_t srr_dstip[16]; /* VL3 Destination IP. */
249 } svp_route_req_t;
250
251 /*
252 * The far-remote Triton Data Center will answer with the requisite information
253 * to send overlay packets to the appropriate far-remote CNs.
254 */
255 typedef struct svp_route_ack {
256 uint32_t sra_dcid; /* Far-remote Data Center ID. */
257 uint32_t sra_vnetid; /* Far-remote vnet ID. */
258 uint16_t sra_vlan; /* Far-remote VLAN ID. */
259 uint16_t sra_port; /* Destination UL3 port. */
260 uint8_t sra_ip[16]; /* Destination UL3 address. */
261 uint8_t sra_srcmac[ETHERADDRL]; /* Far-remote VL2 source. */
262 uint8_t sra_dstmac[ETHERADDRL]; /* Far-remote VL2 dest. */
263 uint8_t sra_src_pfx; /* Far-remote VL3 source prefix */
264 uint8_t sra_dst_pfx; /* Far-remote VL3 dest. prefix */
265 } svp_route_ack_t;
266
267 #ifdef __cplusplus
268 }
269 #endif
270
271 #endif /* _LIBVARPD_SVP_PROT_H */
|
57 SVP_R_BULK_REQ = 0x07,
58 SVP_R_BULK_ACK = 0x08,
59 SVP_R_LOG_REQ = 0x09,
60 SVP_R_LOG_ACK = 0x0A,
61 SVP_R_LOG_RM = 0x0B,
62 SVP_R_LOG_RM_ACK = 0x0C,
63 SVP_R_SHOOTDOWN = 0x0D,
64 SVP_R_ROUTE_REQ = 0x0E,
65 SVP_R_ROUTE_ACK = 0x0F
66 } svp_op_t;
67
68 typedef enum svp_status {
69 SVP_S_OK = 0x00, /* Everything OK */
70 SVP_S_FATAL = 0x01, /* Fatal error, close connection */
71 SVP_S_NOTFOUND = 0x02, /* Entry not found */
72 SVP_S_BADL3TYPE = 0x03, /* Unknown svp_vl3_type_t */
73 SVP_S_BADBULK = 0x04 /* Unknown svp_bulk_type_t */
74 } svp_status_t;
75
76 /*
77 * A client issues the SVP_R_VL2_REQ whenever it needs to perform a VL2->UL3
78 * lookup. Requests have the following structure:
79 */
80 typedef struct svp_vl2_req {
81 uint8_t sl2r_mac[ETHERADDRL];
82 uint8_t sl2r_pad[2];
83 uint32_t sl2r_vnetid;
84 } svp_vl2_req_t;
85
86 /*
87 * This is the message a server uses to reply to the SVP_R_VL2_REQ. If the
88 * destination on the underlay is an IPv4 address, it should be encoded as an
89 * IPv4-mapped IPv6 address.
90 */
91 typedef struct svp_vl2_ack {
92 uint16_t sl2a_status;
93 uint16_t sl2a_port;
94 uint8_t sl2a_addr[16];
95 } svp_vl2_ack_t;
96
97
236 /*
237 * A route-request (SVP_R_ROUTE_REQ) queries the local SVP server to get a
238 * far-remote (i.e. another Triton Data Center, nee. SDC) SVP server for
239 * far-remote networks. Modern overlay modules will request IP destinations
240 * for remote-Triton networks, but they must know how to reach the
241 * remote-Triton SVP server.
242 */
243 typedef struct svp_route_req {
244 uint32_t srr_vnetid; /* Requester's vnet ID. */
245 uint16_t srr_vlan; /* Requester's VLAN ID. */
246 uint16_t srr_pad; /* Zero on xmit, ignore on receipt. */
247 uint8_t srr_srcip[16]; /* VL3 Source IP. */
248 uint8_t srr_dstip[16]; /* VL3 Destination IP. */
249 } svp_route_req_t;
250
251 /*
252 * The far-remote Triton Data Center will answer with the requisite information
253 * to send overlay packets to the appropriate far-remote CNs.
254 */
255 typedef struct svp_route_ack {
256 uint32_t sra_status; /* Status. */
257 uint32_t sra_dcid; /* Far-remote Data Center ID. */
258 uint32_t sra_vnetid; /* Far-remote vnet ID. */
259 uint16_t sra_vlan; /* Far-remote VLAN ID. */
260 uint16_t sra_port; /* Destination UL3 port. */
261 uint8_t sra_ip[16]; /* Destination UL3 address. */
262 uint8_t sra_srcmac[ETHERADDRL]; /* Far-remote VL2 source. */
263 uint8_t sra_dstmac[ETHERADDRL]; /* Far-remote VL2 dest. */
264 uint8_t sra_src_pfx; /* Far-remote VL3 source prefix */
265 uint8_t sra_dst_pfx; /* Far-remote VL3 dest. prefix */
266 } svp_route_ack_t;
267
268 #ifdef __cplusplus
269 }
270 #endif
271
272 #endif /* _LIBVARPD_SVP_PROT_H */
|