[cisco-voip] UCS-E and using both internal and external connections.

[Chris Osborne (Americas)]

Lelio

I’m my experience you will have two internal (router) interfaces to the E140 blade 2/0 and 2/1 plus an external NIC on the card blade itself (I’ve never used it, couldn’t find a reason to)

So you could definitely setup one NIC as internal and the other as External inside the router and or use the external NIC as well as a backup to switch.

Vmware just see’s the 3 NIC’s and you can use them as you see fit with VSwitch setups as normal UCS seriers servers.


Chris Osborne
Sr Solution Architect
T: 704-969-2771
M: 864-423-8288
E: chris.osborne at dimensiondata.com<mailto:chris.osborne at dimensiondata.com>
For more information, please go to www.dimensiondata.com/en-US<http://www.dimensiondata.com/en-US>






From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Saturday, September 09, 2017 9:49 PM
To: cisco-voip voyp list <cisco-voip at puck.nether.net>
Subject: [cisco-voip] UCS-E and using both internal and external connections.





I'm in the process of designing a new demployment of four ucs-E blades (e140s-m2) into four ISR-G2 routers (2x3945,1x3925,1x2921).

The question I have is whether or not I can use _both_ an internal interface and external interface to communicate with the blade? External for ESXi and internal for guests (unity express) running on ESXi.

I'd like to use external for ESXi to stick with existing models but to also remove the router internals as a failure point. The guest itself would need to talk with the router internals to ensure unity express can register with SRST without any infrastructure requirements.

What are people's thoughts about this?

Sent from my iPhone
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170912/d739b2ea/attachment.html>