Another “Why doesn’t Cisco…?” post?

On Twitter, @timmylevad said he’d like to see another “Why doesn’t Cisco?” post like I did .

So this is a request for your ideas on what you’d like to see in such a post. I’ll try to answer as many as I can. Please add your suggestions as a comment to this post.

4 thoughts on “Another “Why doesn’t Cisco…?” post?”

  1. Why can’t we rename objects in UCS? Every client we deploy this for asks for the ability to rename objects. And not just Service Profiles, but all objects.

  2. [Disclaimer – I work @ Cisco]

    The reason you can’t easily rename all objects in UCS is because the name are actual SAM.db objects. Unfortunately in the design of UCS engineering didn’t include an “alias” or logical identifier to UCS objects. In this case we can’t just rename objects without harming the integrity of the system.

    In the upcoming 2.1 release we add support for Service Profile renaming (we’ve been asking for this for years) and it seems to be the #1 pain point for customers. Other objects are such as big deal to re-create.

    Think of it as motivation for proper planning 😛

  3. I wish Cisco would produce and deliver a proper rails for the Fabric Interconnects. To be hounest we were kind of dissapointed/shocked about the simple and very unhandy brackets that came with it. Please see this as good feedback, not complaining.

Leave a Reply

Your email address will not be published. Required fields are marked *