Wired Intelligent Edge

Interesting... I heard for years people complaining that moving from another brand to HPE Aruba Networking was hard. AOS-CX changed a bit to what other vendors in the market do configuration wise to make it easier. Others can probably explain it much better, but for me the main difference between ArubaOS Switch (like the 3810) and AOS-CX (like CX6300) is that in ArubaOS Switch you have VLANs that you provide with an IP address then add ports to the VLAN (tagged or untagged), with AOS-CX you have interfaces and you add VLANs to it, tagged or untagged. But IP config is done on the VLAN/VLAN-interface and speeds on the interface as that is the physical connection to the outside world. And one other big difference on ArubaOS Switch, a trunk is combining multiple phystical interfaces to one logical interface. On AOS-CX that's called a Link Aggregation (LAG). And 'switchport mode trunk' on AOS-CX is about which VLANs should be tagged on the interface (or lag). If you are not aware of the difference in terminology, you may indeed get confused.

If you want to learn more, there is a nice guide that has side-by-side the ArubaOS-Switch commands and the AOS-CX commands.

Also, here are some nice lab guides that get you started, using the AOS-CX Switch simulator.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.

Interesting... I heard for years people complaining that moving from another brand to HPE Aruba Networking was hard. AOS-CX changed a bit to what other vendors in the market do configuration wise to make it easier. Others can probably explain it much better, but for me the main difference between ArubaOS Switch (like the 3810) and AOS-CX (like CX6300) is that in ArubaOS Switch you have VLANs that you provide with an IP address then add ports to the VLAN (tagged or untagged), with AOS-CX you have interfaces and you add VLANs to it, tagged or untagged. But IP config is done on the VLAN/VLAN-interface and speeds on the interface as that is the physical connection to the outside world. And one other big difference on ArubaOS Switch, a trunk is combining multiple phystical interfaces to one logical interface. On AOS-CX that's called a Link Aggregation (LAG). And 'switchport mode trunk' on AOS-CX is about which VLANs should be tagged on the interface (or lag). If you are not aware of the difference in terminology, you may indeed get confused.

If you want to learn more, there is a nice guide that has side-by-side the ArubaOS-Switch commands and the AOS-CX commands.

Also, here are some nice lab guides that get you started, using the AOS-CX Switch simulator.

Thank you, that "Intro and interoperability" document is what I was looking for, strange that thios was only just published. It seems that was something that would be needed from day one.

Now all I need to find out if there is a bug in that documentation because some mentioned I need to not just use vlan trunk allowed <vlans> but alsso an aditional tag parameter. Hoewever that does not seems to be in the docs so I will test it first as shown in this document.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.

Interesting... I heard for years people complaining that moving from another brand to HPE Aruba Networking was hard. AOS-CX changed a bit to what other vendors in the market do configuration wise to make it easier. Others can probably explain it much better, but for me the main difference between ArubaOS Switch (like the 3810) and AOS-CX (like CX6300) is that in ArubaOS Switch you have VLANs that you provide with an IP address then add ports to the VLAN (tagged or untagged), with AOS-CX you have interfaces and you add VLANs to it, tagged or untagged. But IP config is done on the VLAN/VLAN-interface and speeds on the interface as that is the physical connection to the outside world. And one other big difference on ArubaOS Switch, a trunk is combining multiple phystical interfaces to one logical interface. On AOS-CX that's called a Link Aggregation (LAG). And 'switchport mode trunk' on AOS-CX is about which VLANs should be tagged on the interface (or lag). If you are not aware of the difference in terminology, you may indeed get confused.

If you want to learn more, there is a nice guide that has side-by-side the ArubaOS-Switch commands and the AOS-CX commands.

Also, here are some nice lab guides that get you started, using the AOS-CX Switch simulator.

When following the link above, for some kind of reason I cannot find that intro and interop document anymore...

Was it un-published or so? Can you post the link again to the document pls?

Thank you, that "Intro and interoperability" document is what I was looking for, strange that thios was only just published. It seems that was something that would be needed from day one.

Now all I need to find out if there is a bug in that documentation because some mentioned I need to not just use vlan trunk allowed <vlans> but alsso an aditional tag parameter. Hoewever that does not seems to be in the docs so I will test it first as shown in this document.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.

Interesting... I heard for years people complaining that moving from another brand to HPE Aruba Networking was hard. AOS-CX changed a bit to what other vendors in the market do configuration wise to make it easier. Others can probably explain it much better, but for me the main difference between ArubaOS Switch (like the 3810) and AOS-CX (like CX6300) is that in ArubaOS Switch you have VLANs that you provide with an IP address then add ports to the VLAN (tagged or untagged), with AOS-CX you have interfaces and you add VLANs to it, tagged or untagged. But IP config is done on the VLAN/VLAN-interface and speeds on the interface as that is the physical connection to the outside world. And one other big difference on ArubaOS Switch, a trunk is combining multiple phystical interfaces to one logical interface. On AOS-CX that's called a Link Aggregation (LAG). And 'switchport mode trunk' on AOS-CX is about which VLANs should be tagged on the interface (or lag). If you are not aware of the difference in terminology, you may indeed get confused.

If you want to learn more, there is a nice guide that has side-by-side the ArubaOS-Switch commands and the AOS-CX commands.

Also, here are some nice lab guides that get you started, using the AOS-CX Switch simulator.

I can still see the document, as an attachment in the reply by Holger Hasenaug.I can still open it. If you do not see the reply Holger Hasenaug posted go back to the discussion list to see my original post and then go down in the replies.

When following the link above, for some kind of reason I cannot find that intro and interop document anymore...

Was it un-published or so? Can you post the link again to the document pls?

Thank you, that "Intro and interoperability" document is what I was looking for, strange that thios was only just published. It seems that was something that would be needed from day one.

Now all I need to find out if there is a bug in that documentation because some mentioned I need to not just use vlan trunk allowed <vlans> but alsso an aditional tag parameter. Hoewever that does not seems to be in the docs so I will test it first as shown in this document.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.

I can still see the document, as an attachment in the reply by Holger Hasenaug.I can still open it. If you do not see the reply Holger Hasenaug posted go back to the discussion list to see my original post and then go down in the replies.

When following the link above, for some kind of reason I cannot find that intro and interop document anymore...

Was it un-published or so? Can you post the link again to the document pls?

Thank you, that "Intro and interoperability" document is what I was looking for, strange that thios was only just published. It seems that was something that would be needed from day one.

Now all I need to find out if there is a bug in that documentation because some mentioned I need to not just use vlan trunk allowed <vlans> but alsso an aditional tag parameter. Hoewever that does not seems to be in the docs so I will test it first as shown in this document.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.

Interesting... I heard for years people complaining that moving from another brand to HPE Aruba Networking was hard. AOS-CX changed a bit to what other vendors in the market do configuration wise to make it easier. Others can probably explain it much better, but for me the main difference between ArubaOS Switch (like the 3810) and AOS-CX (like CX6300) is that in ArubaOS Switch you have VLANs that you provide with an IP address then add ports to the VLAN (tagged or untagged), with AOS-CX you have interfaces and you add VLANs to it, tagged or untagged. But IP config is done on the VLAN/VLAN-interface and speeds on the interface as that is the physical connection to the outside world. And one other big difference on ArubaOS Switch, a trunk is combining multiple phystical interfaces to one logical interface. On AOS-CX that's called a Link Aggregation (LAG). And 'switchport mode trunk' on AOS-CX is about which VLANs should be tagged on the interface (or lag). If you are not aware of the difference in terminology, you may indeed get confused.

If you want to learn more, there is a nice guide that has side-by-side the ArubaOS-Switch commands and the AOS-CX commands.

Also, here are some nice lab guides that get you started, using the AOS-CX Switch simulator.

There is not partner only information in there and the Airheads Community is public (registration required) therefore also for customers.  So you can share it. 

I can still see the document, as an attachment in the reply by Holger Hasenaug.I can still open it. If you do not see the reply Holger Hasenaug posted go back to the discussion list to see my original post and then go down in the replies.

When following the link above, for some kind of reason I cannot find that intro and interop document anymore...

Was it un-published or so? Can you post the link again to the document pls?

Thank you, that "Intro and interoperability" document is what I was looking for, strange that thios was only just published. It seems that was something that would be needed from day one.

Now all I need to find out if there is a bug in that documentation because some mentioned I need to not just use vlan trunk allowed <vlans> but alsso an aditional tag parameter. Hoewever that does not seems to be in the docs so I will test it first as shown in this document.

The configuration of AOS-CX switches is interface-based compared to AOS-S switches which is more VLAN/feature-based. The below presentation should give you some information on how you deal with interoberability between AOS-CX and AOS-S switches. 
The manuals "AOS-CX 10.13 Layer-2 Bridging Guide" have comparing VLAN commands between the two operating systems. 
There are also free online courses for switching and the HPE book store for more information, see end of presentation.

Once you have a bit of experience you will find the new CLI much more consistent than the former one. Especially using "interface ranges" speed up configuring a device.