Cisco Smartnet for WS-C3750X-48P-S switch.
Hello,
One of my collegues states that:
"With the new 3750X and 3560X Switches you do not have to purchase SmartNET as they are covered by 24X7 hardware replacement for the live of the switch."
I do have 2x 3750X stacked, so I'd like to make sure if this is true? If so how does it work?
Thank you,
forman
forman
This is a very interesting question that may have several subtle issues in the answer. I am giving a URL to a Cisco document that discusses the limited lifetime warranty for the 3750X switches.
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps10745/product_bulletin_c25-607000.html
What I get from reading this includes these points:
- this applies to switches running the base feature sets. If you need some feature available only in IP Services image then you need SMARTnet.
- you have coverage for hardware problems for the lifetime of the switch.
- the hardware coverage provides next business day replacement. Some networks need replacements more quickly that this. What are the requirements for replacement time for your network?
- the warranty provides updates to software, maintenance releases and bug fixes, but upgrades require a maintenance contract.
- the limited warranty gives you only 90 days of TAC support.. You will get bug fixes as they are released, but what do you do if you have the limited warranty and believe that you are running into a new bug?
Some networks will look at the situation and will be happy with just the limited warranty while other networks will consider the restrictions and uncertainty and decide that SMARTnet is worth it. Where does your network fall in this consideration?
HTH
Rick
Similar Messages
-
Difference between Cisco C3750X-48P-L and C3750X-48P-S ?
what is the differance between the WS-C3750X-48P-L and the WS-C3750X-48P-S also do these all include a smartnet?
The difference is the software image licensed. The -L signifies LAN Base and the -S signifies IP Base. You can read up on the features of both from here: http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-3750-x-series-switches/qa_c67-578933.html
All Cisco devices are eligible for SmartNet coverage - but you have to pay depending on how long and what type of service you want. All Cisco switches also come with a limited lifetime warranty now but the replacement time is usually 2-3 weeks in my experience. -
Cisco Architectures for 2950/2960 Switches and 2800 Routers
Hello,
I have a question regarding the architectures of these three series, i.e. the type of switch fabric they use and the general architecture (first, second, or third generation regarding the sharing of the bus, memory and the type of switch fabric). We have so far learned these three generation and our assumption is that the only generation being produced now is the third (crossbar) generation, but so far we have to information to back up this claim. We are doing a study on buffer sizing in edge routers/switches so knowing the exact architecture of each model is our priority.
Thank you for reading and thanks in advance for the answers.Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Exact details on Cisco switch and/or router architecture can be hard to come by, as much of the information, Cisco appears to consider proprietary.
Most switches have some kind of cross bar architecture. Overall bandwidth tends to be higher in later variants (to support higher port densities and/or higher bandwidth ports). Later switch architectures are less likely to block at ports. However, there are often other architecture changes which may improve or worsen performance. For example, 2960 tends to have more fabric bandwidth than the 2950, but the 2960 has different port buffer management (I believe) from the 2950, often resulting in more port drops with bursty traffic.
True routers, like the 2800 series, I believe use a PCI bus, with additional bandwidth restrictions to the modules. They will well support the WAN bandwidths they are recommended for, but they do not well support LAN port bandwidths. Again, specific architecture details can be hard to come by. -
Cisco ISE for 802.1x (EAP-TLS)
I work for a banking organization and security is an area that needs to be improved continuously. I am planning on implementing Cisco ISE for 802.1x together with a Microsoft PKI for certificate issuing and signing.
I am currently trying to implement this in our test environment and I have managed to do a few basic bootstrapping tasks. I need someone to push me into the right direction as to how I can achieve what i am seeking.
I will use Cisco 2900 series switches on the access layer and a few HP switches as well which supports 802.1x.
I want to configure the ISE to process authentication requests using 802.1x EAP-TLS (Certificate Based). All the workstations on the domain needs to authenticate itself using the certificates issued to it by the Certificate Issuing Authority.
I have already managed to get the PKI working and have rolled out the certificates on all the workstations on the test environment. I can't seem to configure the Authentication portion on the ISE.
I request if someone can guide me or direct me to materials that can help achieve the above requirements. The guides available on the Cisco website are overwhelming and I can't seem to figure out how I am supposed to configure the authentication portion.
My email: [email protected]
Cheers,
Krishil ReddyHello Mubashir,
Many timers can be modified as needed in a deployment. Unless you are experiencing a specific problem where adjusting the timer may correct unwanted behavior, it is recommended to leave all timers at their default values except for the 802.1X transmit timer (tx-period).
The tx-period timer defaults to a value of 30 seconds. Leaving this value at 30 seconds provides a default wait of 90 seconds (3 x tx-period) before a switchport will begin the next method of authentication, and begin the MAB process for non-authenticating devices.
Based on numerous deployments, the best-practice recommendation is to set the tx-period value to 10 seconds to provide the optimal time for MAB devices. Setting the value below 10 seconds may result in the port moving to MAC authentication bypass too quickly.
Configure the tx-period timer.
C3750X(config-if-range)#dot1x timeout tx-period 10 -
Configuring Cisco ASA for site to site VPN ( Issue with setting up local network)
OK, so our primary firewall is a checkpoint gateway. Behind that we have a cisco ASA for vpn users. I have a project at the moment where we need to connect to another company using site to site VPN through the cisco ASA, as the checkpoint gateway is unable to establish a permanent tunnel with the other companies Cisco ASA.
What would be the best practise for setting up the local network on my side? Create the network on the ASA and then use a L2 vlan to connect to the Core switch?
Setup a L3 interface on the core switch and point it towards the checkpoint gateway which would then point to the ASA?
When you have to select your local network through the site to site wizard do you have to put the inside network address of the ASA?
Our network is setup like this: Access layer switch > Core 6500 Switch > Checkpoint-Firewall > Internet
The ASA is connected to a checkpoint sub interface
Any help would be beneficial as im new to cisco ASAs
Thanks
MarkMark
If we understood more about your environment we might be able to give you better answers. My initial reaction was similar to the suggestion from Michael to use a L2 vlan. But as I think a bit more my attention is drawn to something that you mention in the original post. The ASA is there for VPN users. If the VPN users need to access your internal network then you probably already have something configured on the ASA that allows access to the internal network. Perhaps that same thing might provide access for your site to site VPN?
HTH
Rick -
Ask the Expert: Cisco TelePresence for the Enterprise
Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco Telepresence® for the enterprise.
Cisco experts Jaret, Fernando, and Fred will be covering all Cisco TelePresence products. Topics include Cisco TelePresence endpoints and TelePresence infrastructure such as the Cisco TelePresence Video Communication Server (VCS), Cisco Expressway Series, Cisco Unified Communication Manager (CallManager), Cisco TelePresence Servers (MSE 8710, on Virtual Machine, etc.), MCU (MSE 8510, etc.), Cisco TelePresence Management Suite (TMS), and all other Cisco TelePresence related devices.
Jaret Osborne is an 8-year Cisco Advanced Services veteran. In his Advanced Services tour, Jaret has covered all aspects of Cisco Unified Communications and TelePresence products, including both enterprise and service provider verticals. Most recently Jaret has been working with global service providers supporting their Cisco TelePresence as a Service offerings while also incubating new cloud services at Cisco.
Fernando Rivas is a Cisco Advanced Services NCE, starting in the Cisco Technical Assistance Center (TAC), 2007, on the Collaboration Technology Team mastering the Cisco Unified Communication technologies and specialized in call control CUCM,VCS) and conferencing (MeetingPlace, Telepresence). In 2011, he joined Cisco Advanced Services as a member of the Cisco Collaboration team and participated in several Cisco TelePresence and video-related technologies deployments. Currently he is a member of the Video Cloud Technology Team, supporting video exchanges in several and architecting new private video cloud solutions for large enterprises. Fernando holds a routing and switching CCIE® certification (22975).
Fred Mollenkopf is a Cisco Advanced Services Network consulting engineer working at Cisco for the last 7 years. Fred has led some of the largest Cisco Unified Communication and Collaboration deployments done for Cisco customers and partners. Over 15 years’ experience in data networking with a specialization in Cisco Unified Communications in 2004. Currently he is a member of the SP Video Advanced Services Team, supporting SP video exchanges and the Cisco Telepresence solutions. Fred maintains an active CCIE® in Voice (17521).
Remember to use the rating system to let Jaret, Fernando, and Fred know if you have received an adequate response.
Because of the volume expected during this event, Jaret, Fred, and Fernando might not be able to answer every question. Remember that you can continue the conversation in the Collaboration, Voice and Video Community, under the sub-community TelePresence, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.Tenaro,
Additionally here are the most common login issues. Unfortunately this includes items related to Presence implementation but I commented where we did not use these in our lab setup for CUCM Phone Capabilities only.
Login Issues
Problem:
Jabber Unable to Sign-in Through MRA
Solution
This can be caused by a number of things, a few of which are outlined below.
1. Collaboration Edge SRV record not created and/or port 8443 unreachable
For a jabber client to be able to login successfully using MRA, a specific collaboration edge SRV record must be created and accessible externally. When a jabber client is initially started it will make server DNS SRV queries:
_cisco-uds : this SRV record is used to determine if a CUCM server is available.
_cuplogin : this SRV record is used to determine if an IM&P server is available.
_collab-edge : this SRV record is used to determine if MRA is available.
If the jabber client is started and does not receive an SRV answer for _cisco-uds and _cuplogin, and does receive an answer for _collab-edge then it will use this answer to try to contact the Expressway-E listed in the SRV answer.
The _collab-edge SRV record should point to the FQDN of the Expressway-E using port 8443. If the _collab-edge SRV is not created, or is not externally available, or if it is available, but port 8443 is not reachable, then the jabber client will fail to login.
2. Unacceptable or No Available Certificate on VCS Expressway
After the jabber client has received an answer for _collab-edge, it will then contact the expressway using TLS over port 8443 to try to retrieve the certificate from the expressway to setup TLS for communication between the jabber client and the expressway.
If the Expressway does not have a valid signed certificate that contains either the FQDN or domain of the Expressway, then this will fail and the jabber client will fail to login.
If this is occurring, the you should use the CSR tool on the Expressway, which will automatically include the FQDN of the expressway as a Subject Alternative Name.
MRA requires secure communication between the Expressway-C and Expressway-E, and between the Expressway-E and external endpoints.
Expressway-C Server Certificate Requirements:
The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation. The Expressway-C should automatically include these in the CSR provided that an IM&P server has already been discovered on the Expressway-C.
The names in FQDN format of all Phone Security Profiles in CUCM configured for TLS and used on devices configured for MRA. This allows for secure communication between the CUCM and Expressway-C for the devices using those Phone Security Profiles.
Expressway-E Server Certificate Requirements:
All domains configured for Unified Communications. This includes the domain of the Expressway-E and C, e-mail address domain configured for Jabber, and any presence domains.
The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation.
The MRA Deployment guide describes this in greater detail on pages 17-18. (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Ac...
Note: In our lab for testing Phone Capabilities only, we did not include the Chat Node Aliases in the certificate as we were not using IM&P.
3. No UDS Servers Found in Edge Config
After the Jabber client successfully establishes a secure connection with the Expressway-E, it will ask for its edge config. This edge config will contain the SRV records for _cuplogin and _cisco-uds. If these SRV records are not returned in the edge config, then the jabber client will not be able to proceed with trying to login.
To fix this, make sure that _cisco-uds and _cuplogin SRV records are created internally and resolvable by the Expressway-C
More information on the DNS SRV records can be found on page 10 of the MRA deployment guide for X8.1.1 (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Access-via-Expressway-Deployment-Guide-X8-1-1.pdf)
Note: In our lab for testing Phone Capabilities only, we did not include the DNS SRV for _cuplogin.
4. The Expressway-C logs will indicate the following error: XCP_JABBERD Detail="Unable to connect to host '%IP%', port 7400:(111) Connection refused"
If Expressway-E NIC is incorrectly configured, this can cause the XCP server to not be updated. If the Expressway-E meets the following criteria, then you will likely have this issue:
Using a single NIC
Advanced Networking Option Key is installed
Use Dual Network Interfaces option is set to “Yes”
To correct this problem, change the “Use Dual Network Interfaces” option to “No”
The reason this is a problem is because the Expressway-E will be listening for the XCP session on the wrong network interface, which will cause the connection to fail/timeout. The Expressway-E listens on TCP port 7400 for the XCP session. You can verify this by using the netstat command from the VCS as root.
Note: We used a Dual Network Interface Expressway for testing but were not using XCP, so this was not applicable to us.
5. VCE-E Server hostname/domain name does not match what is configured in the _collab-edge SRV.
If the Expressway-E Server hostname/domain name does not match what was received in the _collab-edge SRV answer, the jabber client will not be able to communicate to the Expressway-E. The Jabber client uses the xmppEdgeServer/Address element in the get_edge_config response to establish the XMPP connection to the Expressway-E.
This is an example of what the xmppEdgeServer/Address would look like in the get_edge_config response from the Expressway-E to the Jabber client:
<xmppEdgeServer>
<server>
<address>ott-vcse1.vcx.cisco.com</address>
<tlsPort>5222</tlsPort>
</server>
</xmppEdgeServer>
To avoid this, make sure that the _collab-edge SRV record matches the Expressway-E hostname/domain name. Enhancement CSCuo83458 has been filed for this.
Note: This was one of our issues when we first setup. We adjusted our Expressway-E to insure the below:
System > Administration > System Name this was the FQDN
System > DNS > System Host Name was the host portion of the FQDN
System > DNS > Domain Name was the domain portion of the FQDN
System > Clustering > Cluster Name (FQDN for Provisioning) was the FQDN
6. Unable to log into certain IM&P servers. VCS logs say "No realm found for host cups-example.domain.com, check connect auth configuration"
From the Expressway-E, go to Configuration -> Unified Communications -> IM&P Servers. Open each server and click "Save" again. Not sure exactly why this happens.
Note: This was N/A to our test and can be ignored with Phone Capabilities only.
Thanks
Fred -
Cisco Network Assistant, unable to add a switch
I have a network running some 20 switches, two controllers and many AP's. All the devices that should be able to connect to cisco network assistant can successfully. However there is one switch that will show in neighbours but will give the message of “unable to connect to device” when I try and add it to the topology.
As far as I can see the config is identically to all other similar switches in the network. I can telnet from a switch (management VLAN) to the switch in question. However when I try to ping or telnet from the PC running network assistant (different subnet) I am unsuccessful. However I can ping/telnet to all other cisco device from this PC.
The switch is a WS-C3560-48TS and I have included the config for firstly the switch in question and another switch of the same model and config that works correctly. Any help would be greatly appreciated, thank you.
sho run
Building configuration...
Current configuration : 7363 bytes
version 12.2
no service pad
service timestamps debug datetime localtime
service timestamps log datetime localtime
service password-encryption
hostname wc3_switch_1
enable secret 5 $1$Fn0U$2rG6DadA8JSUzQzSNmMc4/
enable password 7 1511021F0725
username dis privilege 15 secret 5 $1$b3d.$S43CM1xtXyEtO5Rsil6Bn1
username admin privilege 15 password 7 0811185C224C543341
no aaa new-model
ip subnet-zero
ip routing
no ip domain-lookup
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
interface FastEthernet0/1
description ### Connected to Parkside-AP05 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/2
description ### Connected to Parkside-AP06 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/3
description ### Connected to Parkside-AP07 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/4
description ### Connected to Parkside-AP08 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/5
description ### Connected to Parkside-AP12 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/6
description ### Connected to Parkside-AP13 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/7
description ### Connected to Parkside-AP20 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/8
description ### Connected to Parkside-AP21 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/9
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/10
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/11
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/12
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/13
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/14
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/15
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/16
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/17
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/18
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/19
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/20
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/21
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/22
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/23
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/24
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/25
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/26
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/27
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/28
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/29
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/30
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/31
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/32
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/33
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/34
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/35
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/36
description ### Connected to Parkside-AP36 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/37
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/38
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/39
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/40
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/41
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/42
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/43
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/44
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/45
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/46
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/47
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/48
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface GigabitEthernet0/1
description *** Connected to WC2A_Core_Switch ***
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/2
description *** Connected to wc3_switch_2 ***
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/3
shutdown
interface GigabitEthernet0/4
shutdown
interface Vlan1
ip address 10.0.0.31 255.255.255.0
ip default-gateway 10.0.0.254
ip classless
ip http server
control-plane
line con 0
password 7 144711185D07
logging synchronous
login local
line vty 0 4
password 7 144711185D07
logging synchronous
login local
line vty 5 15
password 7 094F471A1A0A
no login
end
wc3_switch_2#sho run
Building configuration...
Current configuration : 7239 bytes
version 12.2
no service pad
service timestamps debug datetime localtime
service timestamps log datetime localtime
service password-encryption
hostname wc3_switch_2
enable secret 5 $1$Sfoj$a6AdO7PI0bP8ERhpWl3OP.
username dis privilege 15 secret 5 $1$D9c6$16yFzETOxBNHiPdTEqkxQ1
username admin privilege 15 password 7 133543002059550E78
no aaa new-model
ip subnet-zero
no ip domain-lookup
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
interface FastEthernet0/1
description ### Connected to Parkside-AP24 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/2
description ### Connected to Parkside-AP27 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/3
description ### Connected to Parkside-AP28 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/4
description ### Connected to Parkside-AP30 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/5
description ### Connected to Parkside-AP31 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/6
description ### Connected to Parkside-AP32 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/7
description ### Connected to Parkside-AP33 ###
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/8
description *** Curric4 VLAN Port ***
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface FastEthernet0/9
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/10
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/11
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/12
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/13
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/14
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/15
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/16
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/17
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/18
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/19
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/20
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/21
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/22
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/23
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/24
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/25
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/26
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/27
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/28
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/29
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/30
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/31
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/32
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/33
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/34
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/35
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/36
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/37
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/38
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/39
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/40
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/41
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/42
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/43
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/44
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/45
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/46
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/47
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface FastEthernet0/48
description *** Curric4 VLAN Port ***
switchport access vlan 6
spanning-tree portfast
interface GigabitEthernet0/1
description *** Connected to wc3_switch_1 ***
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/2
description *** Connected to wc3_switch_3 ***
switchport trunk encapsulation dot1q
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/3
shutdown
interface GigabitEthernet0/4
shutdown
interface Vlan1
ip address 10.0.0.32 255.255.255.0
ip default-gateway 10.0.0.254
ip classless
ip http server
control-plane
line con 0
password 7 135514015A0F
logging synchronous
login local
line vty 0 4
password 7 135514015A0F
logging synchronous
login local
line vty 5 15
no login
endThe switch configurations look pretty straightforward and mostly correct.
I notice that the problem switch has "ip routing" global command. Why is that necessary? You are only using it as a L2 switch, yes? If you use "ip routing" and have no routing process (ospf, eigrp, etc.) running you would need to add a static default route (ip route 0.0.0.0 etc.) and not use the "ip default-gateway" command. Otherwise the switch itself (the SVI) does not know how to leave the management VLAN routing-wise since it is the only L3 interface defined.
(I might also add "ip http authentication local" on each and I'd definitely disable telnet in favor of ssh) -
Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches
with Cisco Expert Vinayak Sudame
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
Remember to use the rating system to let Vinayak know if you have received an adequate response.
Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.Hi Vinayak,
Output of "show cfs internal ethernet-peer database"
Switch 1
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b7:c2:80 [Local]
20:00:54:7f:ee:b6:3f:80 16000005
Total number of entries = 2
Switch 2
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b6:3f:80 [Local]
20:00:54:7f:ee:b7:c2:80 16000005
Total number of entries = 2
Output of "show system internal csm info trace"
Switch 1 in which "show cfs peers" show proper output
Mon Jul 1 05:46:19.145339 (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
Mon Jul 1 05:46:19.145280 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Mon Jul 1 05:46:19.145188 (CSM_T) csm_sp_handle_local_verify_commit(4291):
Mon Jul 1 05:46:19.145131 csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
Mon Jul 1 05:46:19.145071 csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
Mon Jul 1 05:46:19.145011 csm_tl_lock(737):
Mon Jul 1 05:46:19.144955 (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
Mon Jul 1 05:46:19.143819 (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
Mon Jul 1 05:46:19.143761 (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
Mon Jul 1 05:46:19.143699 (CSM_T) csm_sp_get_peer_sync_rev(315):
Mon Jul 1 05:46:19.143641 (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
Mon Jul 1 05:46:19.143582 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Switch 2 in which "show cfs peers" does not show proper output
Mon Jul 1 06:13:11.885354 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
Mon Jul 1 06:13:11.884992 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
Mon Jul 1 06:13:11.884932 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
Mon Jul 1 06:13:11.884872 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
Mon Jul 1 06:13:11.884811 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
Mon Jul 1 06:13:11.884750 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
Mon Jul 1 06:13:11.884690 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
Mon Jul 1 06:13:11.884630 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
Mon Jul 1 06:13:11.884568 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
Mon Jul 1 06:13:11.884207 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733916569.txt
Mon Jul 1 06:13:11.878695 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:13:11.878638 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 06:12:29.527840 (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
Mon Jul 1 06:12:29.513255 (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
Mon Jul 1 06:12:29.513179 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733911262.txt
Mon Jul 1 06:12:29.508859 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:12:29.508803 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 05:53:17.651236 Collecting peer info
Mon Jul 1 05:53:17.651181 Failed to get the argumentvalue for 'ip-address'
Mon Jul 1 05:40:59.262736 DB Unlocked Successfully
Mon Jul 1 05:40:59.262654 Unlocking DB, Lock Owner Details:Client:1 ID:1
Mon Jul 1 05:40:59.262570 (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
Mon Jul 1 05:40:59.262513 DB Lock Successful by Client:1 ID:1
Mon Jul 1 05:40:59.262435 Recieved lock request by Client:1 ID:1
Mon Jul 1 05:40:41.741224 ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
Mon Jul 1 05:40:41.741167 ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
show cfs lock gives no output.
Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
Regards. -
How-to use Cisco DCNM for SAN to manage storage fabric
I recently purchased DCNM for SAN (and LAN), have installed and licensed it. The software is up and running, and I have installed the necessary features & licenses to each of my Nexus 5596UP devices. Unfortunately, I'm not able to make any changes to the fabric from the DCNM SAN client. Am I missing some steps here? Do I need to have fiber connections in place from end points, and the SAN, in order to see/manage the fabric?
Thanks in advance!Did you do a fabric discovery ? have you setup proper accounts on the N5k ?
see
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_2/configuration/guides/fund/DCNM-SAN-LAN_5_2/DCNM_Fundamentals/fmaaa.html -
Can I buy Smartnet for WS-SUP720-3B
Hi,
Can I buy SmartNet for a WS-SUP720-3B (Catalyst 6500/Cisco 7600 Supervisor 720 Fabric MSFC3 PFC3B)?
In the DCT it doesn't show up!
Thanks in advance.You buy Smartnet on the chassis and all the components in the chassis are covered, including the Supervisor.
Hope it helps. -
I recently bought a ASA5505 unlimited user for home use and will it come with the latest firmware/software? (i bought it froma amazon).
Also i'm looking for buying smartnet for this device, i need support as well device replacement (response time doesnt matter), what is the best option i need to buy (i saw i can buy smartnet in CDW)
Thanks for any help.Thanks for the reply. I talked to cisco and they confirmed that i need purchase smartnet as well for my device
I will purchase that smartnet service, will that be covered for lifetime or 1 year?
http://www.cdw.com/shop/products/Cisco-SMARTnet-extended-service-agreement/1078996.aspx -
Power Spec For the WS-C6509-E Switch
I just need to know where to look for the power requirements for the WS-C6509-E Switch.
Hi,
Here you go:
http://www.cisco.com/en/US/products/hw/switches/ps708/prod_bulletin0900aecd8017a5e7.html
" The 6- and 9-slot chassis are designed to scale beyond 4000W power supply configurations. In the future they will support 6000W power supplies.
The minimum power supply required is 2500W or higher (AC or DC) for the 6- and 9-slot chassis."
HTH,
Bobby
*Please rate helpful posts -
I'm interesting on buying a Firefox Smart Phone, but
I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
Something like Cisco Jabber for Android o iOS.
Thanks,Hi Itech,
If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
You may also search Firefox Marketplace for an alternative solution:
* [https://marketplace.firefox.com/]
- Ralph -
Cisco Jabber for Mac - Directory Lookup and Contact Fields
Hello,
After having issues myself with Cisco Jabber for Mac 9.2 specifically with Active Directory lookups not working, or contact information not populating (and therefore not being able to call users from the contact list as no telephone information exists) I am including a sample jabber-config.xml file that works for me.
Please note: there are many different ways to configure this. What I will be showing is the method that works for me and my deployment, which is pretty standard.
As always and as a disclaimer, once again, this is what has worked for my deployment scenario. Always keep backups of your configuration files, and always be mindful of anything you have configured already, especially in the jabber-config.xml file.
Background
My deployment is based on CUCM 9, with 1 publisher and 2 subscribers. I also have a CUCM IM & Presence 9.0 server. This assumes that you have already configured your deployment and Jabber is functioning already, albeit with the aforementioned issues.
As for Active Directory, my deployment will be based on Windows 2008 R2 Domain Controllers running in native 2008 mode. For this example, we will be searching directly against one of the DCs with a Global Catalogue role. Please be aware that in large deployments you will have to plan accordingly with regards to lookup traffic from Jabber clients to the DCs.
Also, as of Cisco Jabber for Mac 9, the client no longer can search via the CUCM internal directory (which may be made of local end users, Active Directory synced users, or a mix of both) and this must be done via a LDAP mechanism.
Scenario
In this deployment scenario, Cisco Jabber for Windows is working properly - you can search and add people from Active Directory, and contacts in your contact list have all the appropriate fields populated from Active Directory. However, when trying the same with Jabber for Mac, Jabber for iPhone or Jabber for iPad you notice that you cannot perform a directory lookup, and if you add people directly (for example, [email protected]) the user only has the IM field populated. No telephone, email or additional information is displayed.
Solution
Whereas Cisco Jabber for Windows uses the EDI mechanism (native Windows), whereby when running from a computer that is on the domain (or in the event that you are search for contacts in another Active Directory domain where a domain trust exists) , Jabber for Mac / iPhone / iPad uses the BDI mechanism.
In this case, you will need to provision a jabber-config.xml file that you will upload to your TFTP server (or Publisher) that will be "downloaded" by your Jabber for Mac client and also used by the iPhone and iPad client. You can configure many options in the jabber-config.xml file, but for this example we will place just the information that we need to order for these clients to request and display Active Directory information.
Please note that the configuration may vary depending on your deployment, but at the very least we will be:
- Configuring a DC where we will perform the lookup.
- Configure credentials that will be used to perform the lookup. This will be an Active Directory account that has read rights on the Active Directory domain. Please note that these credentials are saved in plain text in the file, so ensure that the account that you will be using is not privileged.
- Configure the server port that we will be using to perform the lookup.
- Configure the Search Base. This is basically where we want the directory lookup to happen. You can either choose for this lookup to start at the "base" of the domain (and therefore the search will iterate through all the user accounts and and OUs below the root base) or define a specific OU where you want to search.
Caution!
- There is a current limitation with Cisco Jabber for Mac whereby you can only have 1 search base configured. Please keep this in mind if, like me, you have multiple OUs (like an OU for each company in your organization) and under these OUs you have sub OUs as a user account container.
- If using the top level search base, unless you specify a filter, you will potentially be able to search for all user accounts in the domain. You will need to configure the <BDIBaseFilter> parameter if you want to fine tune your search ability.
Steps
These are the steps I have followed. Other steps or considerations may vary.
- Log in to your TFTP server and download the jabber-config.xml file and keep it as a backup. If you are already using the jabber-config.xml file for other purposes, do not worry - you can add your BDI information parameters inside.
- Remove the jabber-config.xml file
- Edit the jabber-config.xml file and configure thus:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>DOMAIN CONTROLLER IP ADDRESS</BDIPrimaryServerName>
<BDIPresenceDomain>YOUR PRESENCE DOMAIN</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1>YOUR SEARCH BASE</BDISearchBase1>
<BDIConnectionUsername>[email protected]</BDIConnectionUsername>
<BDIConnectionPassword>PASSWORD</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
</Directory>
</config>
For example, let´s assume the following:
- Domain controller IP address is 10.1.1.2 .
- Your presence domain is test.local .
- Your search base will be test.local using the top level of the domain.
- Your username with which you will be doing your searches is called walt . Usually you can either identify walt as test.local\walt or [email protected] . It is always best, in these sort of scenarios, to use the UPN convention so we will be configuring a [email protected] .
- The password is the Active Directory password for the account walt .
- I have disabled TLS in my case. There are issues with the Jabber for Mac client when using other security methods.
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>10.1.1.2</BDIPrimaryServerName>
<BDIPresenceDomain>test.local</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1>DC=test,DC=local</BDISearchBase1>
<BDIConnectionUsername>[email protected]</BDIConnectionUsername>
<BDIConnectionPassword>walt01!</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
</Directory>
</config>
One you have configured the jabber-config.xml file, you will now need to upload it to you TFTP server. Once uploaded, you will need to restart the Cisco TFTP service. Again, my TFTP server is on my CUCM publisher, so:
- I go to Cisco Unified OS Administration on my Publisher server, TFTP File Management and I upload jabber-config.xml to / directory
- I then go to Cisco Unified Serviceability on my Publisher server, I locate the Cisco TFTP service and I restart the service
Once this is done, you can figure up your Jabber for Mac client. As a test, on your Mac (using Terminal) go to:
/Users/username/Library/Application Support/Cisco/Unified Communications/Jabber/Config
In here you will see several files, but what we want to see is jabber-config.xml . As soon as you start the Jabber for Mac client and log in, the jabber-config.xml file will download from your TFTP server and get saved here. When you see it appear, just type in your terminal window more jabber-config.xml and make sure that the output is the same as the xml file you created.
From there, try doing directory search. If you have previously added contacts and they still lack attribute information, you will need to remove them (sometimes it will not refresh properly) and add them again from the directory.
I will be updating this guide and ammending anything that is incorrect, but this is meant to be a quick checklist and steps to get this, at least in the most very basic version, up and running for Jabber for Mac.Hello,
Thanks for this post! It works, I can do lookup and also I can add found contact to contact list and get information about contact from LDAP.
One more question: - I can't get all information about contact. I don't get e.c mobile phone number and more others attributes. I have tried to expand your file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>IP of AD</BDIPrimaryServerName>
<BDIPresenceDomain>Presence Domain</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1> Search Base</BDISearchBase1>
<BDIConnectionUsername>User</BDIConnectionUsername>
<BDIConnectionPassword>Password</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
<BDISipUri>msRTCSIP-PrimaryUserAddress</BDISipUri>
<BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
<BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
<BDIMobilePhone>mobile</BDIMobilePhone>
<BDIHomePhone>homePhone</BDIHomePhone>
<BDIOtherPhone>otherTelephone</BDIOtherPhone>
<BDITitle>title</BDITitle>
<BDICompanyName>company</BDICompanyName>
<BDILocation>co</BDILocation>
<BDIPostalCode>postalCode</BDIPostalCode>
<BDICity>l</BDICity>
<BDIState>st</BDIState>
<BDIStreetAddress>streetAddress</BDIStreetAddress>
</Directory>
</config>
But it didn't help.
When I capture lookup via Wireshark, I can see that Jabbers sends search request with bunch of attributes, but from LDAP answer contains only 8 attributes. (see attached screenshots) -
Cisco Jabber for Windows Voicemail issue
At this I'm in processing of implementation Cisco Jabber UC solution for big Company.
I use CUCM 9.1.2, Cisco IM and Presence 9.1.2, CUC 9.1.2, Cisco Jabber for Windows 9.6.1.
I have issue in Cisco Jabber with VoiceMail Integration - when I leave voice message for any user,
than this message is arrived only him Cisco IP Phone, but not in him Cisco Jabber.
From Cisco Jabber Connectivity status in help menu I see that VoiceMail service is successfully connected
and I see VoiceMail button in Cisco Jabber.
How can I resolve this issue?Have you configured the UC Service profile on CUCM with both Voicemail server and mailbox servers?
Maybe you are looking for
-
How do I use Right Click Functionality in Captivate 5
Hello there, I am trialing Adobe Captivate 5, with a view to purchasing it, and I have been loving it, but have hit a snag. My Right Click actions are not working except with the web preview. I noted from the manual a lot of restrictions and from r
-
I close all Firefox windows. When I try to open another window later I get a message telling me that Firefox is still running and that I need to close all windows or restart my computer. I have this about 3 times a day this past week but prior to tha
-
Hello, i have pro logic 9, phonic midi hub,
hello. i have apple mac book pro, running pro logic 9, just bought a phonic midi hub, so i can connect my alessis dm5 drums, but every time i hit a drum pad it put,s my channel volume down to zero, any help greatly received in this matter very frustr
-
How can I change the default publish preview player from HTML to Flash in Adobe Flash CS5.5??
-
After 10.7.2. update cannot see SD card reader in usb drive. Used to appear on desktop and start iPhoto but now nothing happens. It is recognised by system profiler (usb hub), but cannot find it anywhere. Any ideas?