Not in the default configuration, it's just the internal interface that is used.  If you'd prefer to use the external interfaces instead when you set up the system, there is no issue with that.  (Just remember that ESXi will not forward packets directly between interfaces of a vSwitch). Regards, Andy ... View more

Hi, Yes, the BE6000S has all you need for an installation of up to 150 handsets.  The FXO version comes complete with a 4 port card - although you can add more cards if you need to. The only additional component required, other than the handsets themselves, are the PoE Ethernet switches required to connect them all together. Licensing for the BE6000S is available via the R-CBE6K-K9 part number. Regards, Andy ... View more

Hi Mohammad, OK, this makes sense, at least in part.  Certainly 12 Months SWSS is mandatory for all new license purchases (refer to the BE6000 or UCM UCL Ordering Guides).  However, I also see from your screen shot that there appears to be no service options available - there should be, but as this is driven by your location there may be an issue with your user profile. Could you please make sure that you have all addresses and service preferences completed in your profile.  If that doesn't enable the add services option, please contact Cisco Customer Support to have them check that your profile is correctly set up. Once you are set up correctly, you should select either Cisco SWSS (ECMU) or the partner option (PSBU). Hope that helps, Andy ... View more

Hi Mohammad, When you are selecting SWSS, is that for the server (BE6H-M4-K9=) or for the application licenses (R-CBE6K-K9)? For the server, you should be selecting one of the options from either the Cisco SMART NET TOTAL CARE or PARTNER SUPPORT SERVICE options.  I see that SWSS is available for the server for some reason - it shouldn't be, as it doesn't provide hardware cover (I'll look in to that).  I'm not sure why you are seeing that message though. When configuring your licenses, SWSS (ECMU) or Partner SWSS (PSBU) are certainly the options to consider. Regards, Andy ... View more

Hi Mohammad, When we moved to the new processors for the M4 family, we decided to use 1 8 core CPU, rather than 2 4 core sockets.  The net difference is the same, but it allows more commonality with the BE6H (which has two of those CPUs). It's the same for the disks.  For the 6M there are now more (smaller) SAS drives allowing for a RAID5 configuration.  Again, this drives more alignment with the 6H, which is basically the same, just with more drives. The only reason why you should get an invalid configuration is if the power cable wasn't selected.  Can you check that? Regards, Andy ... View more

Hi Mohammed, That part number is for a refurbished product based on the M3 product specification (it probably wouldn't have any software preinstalled either). The part you need to look for is: BE6M-M4-K9= Regards, Andy ... View more

Should be sometime in the next few weeks. Andy ... View more

Hi, Sounds like a default gateway / routing issue.  I assume that you are using the same voice vlan across the network, so in the context of the default configuration (there are many other ways this could be done), you'd connect to interface Gi0/1.  The IP address for the router would be configured on interface BVI1 and CIMC on ucse1/0 with it's default GW pointing to your subnet DGW IP (sounds like you already did this). So provided that you configure ESXi (and the collaboration applications) with IP addressing in the voice vlan and your DGW / DNS settings you ought to be ok. The alternative, would be to leave the IOS configuration as it is and use your voice VLAN purely external to the BE6000S.  You just then need to connect via Gi0/0 and configure that with an IP from your VVLAN.  To get traffic in and out of the blade, add a route to 172.27.199.0/26 via this Gi0/0 address.  Also add a default gateway / default route to the BE6000S directed to the VVLAN DGW. Make sense? FWIW, see below for a connectivity diagram for the BE6000S - apologies for the quality :-). Andy ... View more

Hi, We are working on a specific BE6000S version of the current install guide.  This will have some of the information you need.  In the meantime, here is a summary of how the BE6000S is configured to use its interfaces. Interface Gi0/0 - Routed interface to the appliance.  By default, this will take an address from DHCP.  Set up routing in your network to get to the default 172.27.199.0/26 subnet via this address. Interface Gi0/1 - Layer 2 interface bridged to the UCS-E blade.  By default if you connect a PC to this port you will get a 172.27.199.0/26 address assigned via DHCP. Interface Gi0/2 and the two external UCSE ports are not used. Hope that helps a little, Andy ... View more

The version 11 offer has also now been updated to align CUWL offers across the business. WebEx SaaS services have now been removed from BE6000 CUWL licenses.  CUWL Pro, now includes updated Personal Multiparty licenses.  As before, remember to order "FIRST-PRO" for first time CUWL-PRO orders to ensure that all video conferencing infrastructure licenses are included. The latest BE6000 Ordering Guide is available here. ... View more