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
------------------------------
Original Message:
Sent: 08-19-2020 04:26 PM
From: BARRY STERN
Subject: ssg_eth1 behaviour on startup OVA template
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
Original Message:
Sent: 08-18-2020 11:51 AM
From: Sebastian van Voorn
Subject: ssg_eth1 behaviour on startup OVA template
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
------------------------------