Layer7 API Management

Expand all | Collapse all

ssg_eth1 behaviour on startup OVA template

  • 1.  ssg_eth1 behaviour on startup OVA template

    Posted 08-18-2020 11:52 AM

    When I deploy an #layer7gateway #version10  OVA template with 2 NICs (at first start) the ssg_eth1 gets the working link.
    Either it is in Vmware connection 1 or 2 it doesn't matter. Why is that?
    This is unlogical, because the working link is of course ssg_eth0! that's the management interface.
    Now we allways have to swap the VLANs after the first boot..

    Can someone explain this behaviour?

    ​​​​​Greetings,

    ------------------------------
    Sebastian van Voorn,
    SR. System Engineer
    RDW
    ------------------------------


  • 2.  RE: ssg_eth1 behaviour on startup OVA template

    Broadcom Employee
    Posted 08-19-2020 04:27 PM
    this is documented here:

    this behavior seems consistent with previous versions where eth0 was the management interface.
    https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/10-0/reference/network-deployment-guide.html



  • 3.  RE: ssg_eth1 behaviour on startup OVA template

    Posted 08-20-2020 09:21 AM

    Hello Barry,

    I don't understand your reply. Maybe I have been not clear enough.
    I have deployed a new Layer7 API gateway using Deploy OVF template (gateway-10.0.00-10442-vmware-centos7-x86_64.ova) in VMware ESXi 6.5.
    During the deploy I connected Network Adapter 1 to our management VLAN.
    After the deploy I added a Network Interface (Network Adapter 2) and connected it to an empty VLAN.
    Then I started the VM and logged in when ready.
    Now the NIC ssg_eth0 has the MAC-address of Network Adapter 2 and
    NIC ssg_eth1 has the MAC address of Network Adapter 1.
    Conclusion: It has switched.
    Very unlogical, because now I have to switch the VLANs on the adapters in Vmware.

    question 1: What is the behaviour Broadcom has experienced in this procedure?

    Another thing that's incorrect described in the documentation is that there now are 2 NICs: ssg_eth0 and ssg_eth1. The 2 domain documentation say there has to be ssg_eth1 and ssg_eth2 and ssg_eth3. What happened to ssg_eth0? How can we manage without ssg_eth0?
    See: Network Deployment Guide 

    question 2: which NICs should appear when you initialy boot a Layer7 API gateway version 10 OVA template with 2 network adapters?

    Greetings,



    ------------------------------
    Sebastian van Voorn,
    SR. System Engineer
    RDW
    ------------------------------



  • 4.  RE: ssg_eth1 behaviour on startup OVA template

    Broadcom Employee
    Posted 08-20-2020 02:44 PM
    Edited by Barry Stern 08-20-2020 02:44 PM
    Hello Sebastian,

    I would recommend opening a support ticket regarding the documentation. It does appear that the information on 2 domains may need to be updated.

    The first time I boot an Appliance with 2 NIC i see them as ssg_eth0 and ssg_eth1.





  • 5.  RE: ssg_eth1 behaviour on startup OVA template

    Posted 08-21-2020 03:11 AM

    I have asked our partner Enable-U to report it to Broadcom the 4th of august.

    Can you confirm this?



    ------------------------------
    SR. System Engineer
    RDW
    ------------------------------