Cisco FabricPath can be integrated into data centers and remote sites. For example, in a bank, we can extend the architecture to remote branches by implementing switches connected to the first and second spine for redundancy. This setup allows for VXLAN, VLAN, and SGT for user authentication. We can also use wireless technology through the data plane and route it on L3. This setup provides scalability and visibility. This technology is deployed in the USA, France, and Europe. For instance, BNP Paribas in France uses this technology.
Cisco FabricPath is functional in both CLI and graphical modes. From an administrator's perspective, having a graphical interface is preferable for its user-friendliness. However, it's important to note that the graphical interface often relies on Java, and compatibility with different versions of Java can be a factor. Older versions of Java may be necessary for compatibility with certain software components. While CLI management is adequate, a graphical interface offers a more intuitive experience, especially in complex environments like FabricPath.
Head of Information Technology at a energy/utilities company with 51-200 employees
Real User
Top 20
2024-01-11T15:08:00Z
Jan 11, 2024
In terms of the series, I find that the integration with other teleconferencing applications needs to be more seamless. I have suggested to Cisco that the endpoint device should allow joining calls from Microsoft Teams, Zoom, and other teleconferencing applications. Additionally, I appreciate the recent inclusion of breakout sessions in the Cisco Webex application, which enhances its relevance in the networking field.
Senior Network Specialist & Project Manager at Elmec Informatica Spa
Real User
Top 5
2023-07-21T10:11:00Z
Jul 21, 2023
We are working on layer 3 integration to completely expand our preferred center. At the moment, we are using VRF on an internal switch, so layer 3 does not have higher availability. I want to see that improve.
Infrastructure and Telecommunications Manager at Boxito
Real User
2022-11-17T23:23:32Z
Nov 17, 2022
I'd like to see better integration with SIEM, perhaps to generate more plugins that can adapt to the traffic analyzer. We also have some issues with the technical support because in Mexico the hardware is not always readily available. We had to wait around 50 days for a part. It's crucial to have sufficient stock on hand for your customers.
The cloud version of Cisco Fabric Path could be improved because most of our clients choose to stay on premises because of the unstable internet service available here.
IT manager at a agriculture with 10,001+ employees
Real User
Top 10
2022-04-11T20:53:44Z
Apr 11, 2022
The price is a little bit too high. They need to work on lowering the cost. The GUI and OpSys would be better. Cisco should focus on something better for the GUI and figure out the interface.
Responsable Infrastructures, Réseaux & Télécoms at a university with 201-500 employees
Real User
2022-02-23T19:33:13Z
Feb 23, 2022
There could always be more interfaces included in the switch. If Cisco can include management for this protocol in Layer 3, that would be ideal. For example, we have our first data center in the USA and the second data center is in Europe. If we could juxtapose FabricPath for managing the Layer 2 loop between these two data centers locally, that would be great.
The documents could improve for Cisco FabricPath. There are times when the relevant information is not present in the different sections of the documents, such as deployment. The documents should be more detailed and enhanced. Having better documentation would benefit the engineers working on the solution.
The exact role that this solution plays, as compared to other products by Cisco, is unclear to our customers. It is sometimes difficult to highlight exactly what individual products are used for and it is something that should be simplified. This product doesn't have its own LAN monitoring tool. There would be more support for this solution if there were options available for those with a smaller budget.
The solution is quite expensive. They should work on lowering the cost to make it more affordable for users. Cisco should add a few more security features to make it more robust. The solution should offer better reporting.
Manager - IT Infrastructure and Network at a manufacturing company with 1,001-5,000 employees
Real User
Top 20
2020-03-05T08:39:00Z
Mar 5, 2020
We are using it to implement security sites. Currently, we are using Fortinet as a UTM, you can say an initial firewall. So we are repeating some issues in Fortinet. So we are looking at other products. If we get a better price then we can think about switching.
CTO at a tech services company with 11-50 employees
Real User
2020-02-09T08:17:00Z
Feb 9, 2020
It's possible that some improvements could be made on specific technical issues such as implementation. The user interface could be improved and perhaps the command line as well. It's nothing too serious. Deployment is on the Cisco site or on the customer's site so it's quite difficult to talk about additional features - each situation is different. Because it's an enterprise environment you can't go in there like an elephant in a glass house, you have to be very careful. It's quite reliable and you know it works in an enterprise environment. There is also quite good support from Cisco in order to resolve some of the issues.
Technical Consultant at a tech services company with 51-200 employees
Reseller
2020-01-26T09:26:00Z
Jan 26, 2020
I personally haven't found anything that is lacking. However, it depends on the use case of the company. It's a good technology. It's only a small part of the complete DC architecture. The pricing could be adjusted to make it easier to sell to clients.
LAN Switching refers to the method of directing data within a local area network using switches, providing efficient data transfer and minimal latency.
Switches operate at Layer 2 of the OSI model, managing data packets using MAC addresses. This enhances network efficiency and ensures data is directed to the correct recipient. Experts note that switches can significantly reduce data collisions compared to hubs, making them crucial for modern high-speed networks.
What are the...
Currently, there are no issues or suggestions for improvement as everything is working smoothly.
Cisco FabricPath can be integrated into data centers and remote sites. For example, in a bank, we can extend the architecture to remote branches by implementing switches connected to the first and second spine for redundancy. This setup allows for VXLAN, VLAN, and SGT for user authentication. We can also use wireless technology through the data plane and route it on L3. This setup provides scalability and visibility. This technology is deployed in the USA, France, and Europe. For instance, BNP Paribas in France uses this technology.
Cisco FabricPath is functional in both CLI and graphical modes. From an administrator's perspective, having a graphical interface is preferable for its user-friendliness. However, it's important to note that the graphical interface often relies on Java, and compatibility with different versions of Java can be a factor. Older versions of Java may be necessary for compatibility with certain software components. While CLI management is adequate, a graphical interface offers a more intuitive experience, especially in complex environments like FabricPath.
Cisco FabricPath's pricing is expensive.
In terms of the series, I find that the integration with other teleconferencing applications needs to be more seamless. I have suggested to Cisco that the endpoint device should allow joining calls from Microsoft Teams, Zoom, and other teleconferencing applications. Additionally, I appreciate the recent inclusion of breakout sessions in the Cisco Webex application, which enhances its relevance in the networking field.
I don't see any weakness in the product. The product lacks AI. AI technology should be involved in Cisco FabricPath's future releases.
We are working on layer 3 integration to completely expand our preferred center. At the moment, we are using VRF on an internal switch, so layer 3 does not have higher availability. I want to see that improve.
The cost of the solution is very high. It was quite expensive. The solution is complex to set up.
I'd like to see better integration with SIEM, perhaps to generate more plugins that can adapt to the traffic analyzer. We also have some issues with the technical support because in Mexico the hardware is not always readily available. We had to wait around 50 days for a part. It's crucial to have sufficient stock on hand for your customers.
I can't speak to any areas that need improvement right now. The solution is costly.
The cloud version of Cisco Fabric Path could be improved because most of our clients choose to stay on premises because of the unstable internet service available here.
The price is a little bit too high. They need to work on lowering the cost. The GUI and OpSys would be better. Cisco should focus on something better for the GUI and figure out the interface.
There could always be more interfaces included in the switch. If Cisco can include management for this protocol in Layer 3, that would be ideal. For example, we have our first data center in the USA and the second data center is in Europe. If we could juxtapose FabricPath for managing the Layer 2 loop between these two data centers locally, that would be great.
The documents could improve for Cisco FabricPath. There are times when the relevant information is not present in the different sections of the documents, such as deployment. The documents should be more detailed and enhanced. Having better documentation would benefit the engineers working on the solution.
The management features are in need of improvement.
I would like one management console to control the network.
The exact role that this solution plays, as compared to other products by Cisco, is unclear to our customers. It is sometimes difficult to highlight exactly what individual products are used for and it is something that should be simplified. This product doesn't have its own LAN monitoring tool. There would be more support for this solution if there were options available for those with a smaller budget.
The solution is quite expensive. They should work on lowering the cost to make it more affordable for users. Cisco should add a few more security features to make it more robust. The solution should offer better reporting.
We are using it to implement security sites. Currently, we are using Fortinet as a UTM, you can say an initial firewall. So we are repeating some issues in Fortinet. So we are looking at other products. If we get a better price then we can think about switching.
It's possible that some improvements could be made on specific technical issues such as implementation. The user interface could be improved and perhaps the command line as well. It's nothing too serious. Deployment is on the Cisco site or on the customer's site so it's quite difficult to talk about additional features - each situation is different. Because it's an enterprise environment you can't go in there like an elephant in a glass house, you have to be very careful. It's quite reliable and you know it works in an enterprise environment. There is also quite good support from Cisco in order to resolve some of the issues.
I personally haven't found anything that is lacking. However, it depends on the use case of the company. It's a good technology. It's only a small part of the complete DC architecture. The pricing could be adjusted to make it easier to sell to clients.
I would like to see better interoperability with other IT solutions. More support staff are required to support Cisco solutions in Italy.