Путеводитель по Руководству Linux

  User  |  Syst  |  Libr  |  Device  |  Files  |  Other  |  Admin  |  Head  |



   vtep    ( 5 )

схема базы данных hardware_vtep (hardware_vtep database schema)

Physical_Switch TABLE

A physical switch that implements a VTEP.

Summary: ports set of Physical_Ports tunnels set of Tunnels Network Status: management_ips set of strings tunnel_ips set of strings Identification: name string (must be unique within table) description string Error Notification: switch_fault_status : mac_table_exhaustion none switch_fault_status : tunnel_exhaustion none switch_fault_status : lr_switch_bindings_fault none switch_fault_status : lr_static_routes_fault none switch_fault_status : lr_creation_fault none switch_fault_status : lr_support_fault none switch_fault_status : unspecified_fault none switch_fault_status : unsupported_source_node_replication none Common Column: other_config map of string-string pairs

Details: ports: set of Physical_Ports The physical ports within the switch.

tunnels: set of Tunnels Tunnels created by this switch as instructed by the NVC.

Network Status:

management_ips: set of strings IPv4 or IPv6 addresses at which the switch may be contacted for management purposes.

tunnel_ips: set of strings IPv4 or IPv6 addresses on which the switch may originate or terminate tunnels.

This column is intended to allow a Manager to determine the Physical_Switch that terminates the tunnel represented by a Physical_Locator.

Identification:

name: string (must be unique within table) Symbolic name for the switch, such as its hostname.

description: string An extended description for the switch, such as its switch login banner.

Error Notification:

An entry in this column indicates to the NVC that this switch has encountered a fault. The switch must clear this column when the fault has been cleared.

switch_fault_status : mac_table_exhaustion: none Indicates that the switch has been unable to process MAC entries requested by the NVC due to lack of table resources.

switch_fault_status : tunnel_exhaustion: none Indicates that the switch has been unable to create tunnels requested by the NVC due to lack of resources.

switch_fault_status : lr_switch_bindings_fault: none Indicates that the switch has been unable to create the logical router interfaces requested by the NVC due to conflicting configurations or a lack of hardware resources.

switch_fault_status : lr_static_routes_fault: none Indicates that the switch has been unable to create the static routes requested by the NVC due to conflicting configurations or a lack of hardware resources.

switch_fault_status : lr_creation_fault: none Indicates that the switch has been unable to create the logical router requested by the NVC due to conflicting configurations or a lack of hardware resources.

switch_fault_status : lr_support_fault: none Indicates that the switch does not support logical routing.

switch_fault_status : unspecified_fault: none Indicates that an error has occurred in the switch but that no more specific information is available.

switch_fault_status : unsupported_source_node_replication: none Indicates that the requested source node replication mode cannot be supported by the physical switch; this specifically means in this context that the physical switch lacks the capability to support source node replication mode. This error occurs when a controller attempts to set source node replication mode for one of the logical switches that the physical switch is keeping context for. An NVC that observes this error should take appropriate action (for example reverting the logical switch to service node replication mode). It is recommended that an NVC be proactive and test for support of source node replication by using a test logical switch on vtep physical switch nodes and then trying to change the replication mode to source node on this logical switch, checking for error. The NVC could remember this capability per vtep physical switch. Using mixed replication modes on a given logical switch is not recommended. Service node replication mode is considered a basic requirement since it only requires sending a packet to a single transport node, hence it is not expected that a switch should report that service node mode cannot be supported.

Common Column:

The overall purpose of this column is described under Common Column at the beginning of this document.

other_config: map of string-string pairs