Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

multiple nics in tripleo

Hi all

I am trying to convert my tripleo-rocky with Vxalns installation from using only 1 NIC to using 4.

The templates used to deploy are the ones provided by tripleo

      network_config:
      - type: ovs_bridge
        name: bridge_name
        use_dhcp: false
        dns_servers:
          get_param: DnsServers
        domain:
          get_param: DnsSearchDomains
        addresses:
        - ip_netmask:
            list_join:
            - /
            - - get_param: ControlPlaneIp
              - get_param: ControlPlaneSubnetCidr
        routes:
        - ip_netmask: 169.254.169.254/32
          next_hop:
            get_param: EC2MetadataIp
        - default: true
          next_hop:
            get_param: ControlPlaneDefaultRoute
        members:
        - type: interface
          name: nic2
          # force the MAC address of the bridge to this interface
          primary: true
        - type: vlan
          vlan_id:
            get_param: StorageNetworkVlanID
          addresses:
          - ip_netmask:
              get_param: StorageIpSubnet
          routes:
            list_concat_unique:
              - get_param: StorageInterfaceRoutes
        - type: vlan
          vlan_id:
            get_param: InternalApiNetworkVlanID
          addresses:
          - ip_netmask:
              get_param: InternalApiIpSubnet
          routes:
            list_concat_unique:
             - get_param: TenantInterfaceRoutes

And I am trying to switch to this.

  params:
    $network_config:
      network_config:
      - type: interface
        name: nic1
        use_dhcp: false
        dns_servers:
          get_param: DnsServers
        domain:
          get_param: DnsSearchDomains
        addresses:
        - ip_netmask:
            list_join:
            - /
            - - get_param: ControlPlaneIp
              - get_param: ControlPlaneSubnetCidr
        routes:
        - ip_netmask: 169.254.169.254/32
          next_hop:
            get_param: EC2MetadataIp
        - default: true
          next_hop:
            get_param: ControlPlaneDefaultRoute
      - type: ovs_bridge
        name: bridge_name
        dns_servers:
          get_param: DnsServers
        members:
        - type: interface
          name: nic3
          # force the MAC address of the bridge to this interface
          primary: true
        - type: vlan
          device: nic3
          vlan_id:
            get_param: TenantNetworkVlanID
          addresses:
          - ip_netmask:
              get_param: TenantIpSubnet
      - type: interface
        name: nic2
        use_dhcp: false
      - type: vlan
        device: nic2
        vlan_id:
          get_param: InternalApiNetworkVlanID
        addresses:
        - ip_netmask:
            get_param: InternalApiIpSubnet
        routes:
          list_concat_unique:
            - get_param: InternalApiInterfaceRoutes
      - type: interface
        name: nic4
        use_dhcp: false
      - type: vlan
        device: nic4
        vlan_id:
          get_param: StorageNetworkVlanID
        addresses:
        - ip_netmask:
            get_param: StorageIpSubnet
        routes:
          list_concat_unique:
            - get_param: StorageInterfaceRoutes

The deployment works and if a spawn a vm the machine is pingable. However the machine is not SSH-able . I am nearly certain that there is some MTU fragmentation somewhere because ping works but ping -s 1373 does not. Therefore there is a 1400 MTU somewhere but I really dont see it. Can somebody please confirm that the template is fine??

P.S.br-ex gets not Ip in my templates which I dont know if it viable