Accepted Solutions
Hi @m1xed0s ,
Old habits die hard eh?
My opinion is that the "new" (5.27(g) and later) way of managing Leaf and Interface Profiles and selectors is the way it SHOULD have been done on day 1.
Now I do have some criticisms - all around the system-dash-something-ridiculously-long-convoluted-names that are used, so that when you looks at narrow list of names they all look the same. SHAME ON YOU CISCO - you should have made the designers use the product first!
Now I've got that off my chest - back to your question.
Whether people like it or not, this is the way it will be done going forward. There's no sense resisting change when Cisco have decided this is the way it is done - yes, you are left with option of continuing your old ways... UNTIL someone gets soooo tempted by that message that appears at the top of the page every time you visit Fabric > Access Policies >> Interface Configuration that tells you are doing things the old way and asks "Would you like me to fix that?"
The moment someone clicks that link (and confirms) then your turning back is like diving your car back up the cliff you just ran off.
And regarding your problem:
I am still preferring the manual approach to define the interface selector and switch selector to configure access ports, PC and vPC. However, one "issue" I ran into with the manual approach is specifying the description for each individual ports, whether they are individual access or a PC member port, if the interface selector has multiple ports included...
Port descriptions in ACI have been a PIA forever - and in the new system (since there are no Leaf Profiles with more than one leaf) VPCs have to have the interface description entreated twice (because there is an Interface Selector for each VPC leaf pair)
BUT if you are still using the old system, the best way to enter a description is go to Fabric > Access Policies >> Interfaces > Leaf Interfaces > Profiles > Your_Leaf_Profile > Your_Interface_Selector and double-click on the port block - be it a single port or a range. If you enter the description there, it should work.
In other words DON'T try and enter the interface description from Fabric > Inventory >> Pod 1 > Your_Leaf > Interfaces > Physical Interfaces > interface-id
Hi @m1xed0s ,
Old habits die hard eh?
My opinion is that the "new" (5.27(g) and later) way of managing Leaf and Interface Profiles and selectors is the way it SHOULD have been done on day 1.
Now I do have some criticisms - all around the system-dash-something-ridiculously-long-convoluted-names that are used, so that when you looks at narrow list of names they all look the same. SHAME ON YOU CISCO - you should have made the designers use the product first!
Now I've got that off my chest - back to your question.
Whether people like it or not, this is the way it will be done going forward. There's no sense resisting change when Cisco have decided this is the way it is done - yes, you are left with option of continuing your old ways... UNTIL someone gets soooo tempted by that message that appears at the top of the page every time you visit Fabric > Access Policies >> Interface Configuration that tells you are doing things the old way and asks "Would you like me to fix that?"
The moment someone clicks that link (and confirms) then your turning back is like diving your car back up the cliff you just ran off.
And regarding your problem:
I am still preferring the manual approach to define the interface selector and switch selector to configure access ports, PC and vPC. However, one "issue" I ran into with the manual approach is specifying the description for each individual ports, whether they are individual access or a PC member port, if the interface selector has multiple ports included...
Port descriptions in ACI have been a PIA forever - and in the new system (since there are no Leaf Profiles with more than one leaf) VPCs have to have the interface description entreated twice (because there is an Interface Selector for each VPC leaf pair)
BUT if you are still using the old system, the best way to enter a description is go to Fabric > Access Policies >> Interfaces > Leaf Interfaces > Profiles > Your_Leaf_Profile > Your_Interface_Selector and double-click on the port block - be it a single port or a range. If you enter the description there, it should work.
In other words DON'T try and enter the interface description from Fabric > Inventory >> Pod 1 > Your_Leaf > Interfaces > Physical Interfaces > interface-id
