AvidXchange is well suited for companies with multiple locations where approvals may be hard to get directly. A user can log on when they have time basically from anywhere to review, code and approve invoices. This would allow for processing of invoices centrally more efficiently then with appear invoices being moved from one place to another to be processed
Fairly stable and easy to operate - but I haven't any experience with other brands, so I don't have anything to compare with. Fairly fast in the OS. Easy to upgrade - but with some SW issues. Sometimes clearing of log folders is needed. Access to bash is cool. Tips & cool tricks for operations could be nice to share.
Our contractors and vendors can submit invoices electronically through AvidBill, removing the tedious task of sorting and coding mail. This feature saves on time and administrative duties.
Communication is key, and being able to log a comment or question in AvidInvoice allows for clarification and expedited approval process.
Having multiple properties, having the Property Code and % Allocation features allow us to ensure the correct entity is charged it's portion of expenses. For example, we may have a service that is coded to all 32 properties. With AvidInvoice we are able to allocate each entity's pro rata share of the invoice.
Maintenance, upgrades, and software certification can be performed without service interruptions because of the modular nature of NX-OS and features such as In-Service Software Upgrade (ISSU) and the capability for processes to restart dynamically
FabricPath:
Enables each device to build an overall view of the topology; this is similar to other link state routing protocols. Each device in the FabricPath topology is identified by a switch-id. The Layer 2 forwarding tables are built based on reachability to each switch-id, not by the MAC address. Eliminates spanning-tree to maximize network bandwidth and flexibility in topological configurations, as well as simplify operational support and configuration. This enables a tremendous amount of flexibility on the topology because you can now build FabricPath topologies for Layer 2-based networks the same as for Layer 3-based networks
Overlay Transport Virtualization (OTV): Enables the Layer 2 extension between distributed data centers over any transport Layer 3 network
AvidPay needs some improvement to minimize the amount of time it takes to issue payment for invoices
The search features within AvidXchange on the advanced search screen sometimes do not function correctly (sorting by ascending / descending order doesn't work all of the time).
The log enhancement follow-up procedure could use some work.
Implementing jumbo frames on interfaces of its fabric extender series (N2k, etc.) by editing the network QoS does not have to be a global configuration that would affect all its interfaces. It can be improved to become just an interface configuration.
Licensing on the NXOS is a bit complicated and expensive. I understand that the Nexus is made for core data center switching but it does not have to break the bank.
OTV technology is for Nexus only. Based on the advantage of the technology, it should be made vendor-neutral to accommodate other vendor devices.
We will use it for a long time, since they are switches with great capacity and positive results, they promote the perfect operation of our data center, I always recommend them, because they are switches with good results.
In our environment (and especially during COVID and the Work From Home era), I would really like our network devices to be more resilient [against} errors in remote configuration. Having a standard, easy to use, configure, commit/deploy, rollback system should be installed, but it's not there. Other companies have been providing this for over 20 years, and Cisco does this on some of their devices. Why not all?
These switches are very fast. They've been designed to work within the data center. We connect them to Cisco UCS-B Mini servers with the storage being directly attached. They are able to handle the data traffic pretty easily. We can also move servers pretty fast from data center to data center without overloading them. This has allowed our company to stay running during any kind of conditional outage. We have come to really rely on them for business continuity.
Overall, Cisco has great products and I believe that they believe in the philosophy of a great customer experience. Although there have been a few technical support issues that caused a lot of company anxiety, in most cases, Cisco has gone above and beyond in making a valiant effort to help the customer solve any issues.
We are presently evaluating a move to Concur Invoice, not because of any real lack of functionality from AvidXchange, but simply because we have other business functions already on Concur Invoice. From what we have seen so far, the functionality is similar, though I believe Concur Invoice is more expensive.
The Cisco 9000 stacks up quite well against the Cisco Catalyst 3850 switches. The additional features available in the Nexus 9000, such as VPN, FCoE, 40 gigabits, give us the ability to support the future needs of the company in our data center. The Nexus 9000 allowed us to condense our core and aggregation environment that comprised of 2 Catalyst 6504 and 2 Catalyst 6509 to a port of Nexus 9000. Although the Catalyst 3850 would be sufficient to handle routing, those features in the Nexus 9000 made it the clear choice for us.
The Nexus 3000 series switches are data center switches, so I would say they have similar security ability to other switches in this segment. I don't have a lot of experience doing more than basic ACL security on switches, but I know these can be integrated into other security solutions like Cisco ISE and 802.1x authentication. It could also be integrated into an ACI solution to add micro segmentation, which would bring in other security functions.
