Cisco Switches (2960 Series) Management

We are managing these devices using HP OpenView Network Node Manager (Ver. 7.5) on HP-UX platform.
What are the known problems, limitations on its initial discovery and on later stages of managing the same ?

The Cisco Catalyst 2960 Series supports the Cisco IOS LAN BASE software image. This software image is a rich suite of intelligent services that is also available in a crypto image at no additional charge.
Cisco Network Assistant also offers centralized management and configuration of Cisco switches and other Cisco devices such as routers and wireless access points. With Cisco Network Assistant, in addition to configuring multiple switches at a time, you can configure Cisco wireless access points, and invoke the Device Manager on Cisco routers and access points. Cisco Network Assistant can be downloaded (available at no cost).
This URL should help you:
http://www.cisco.com/en/US/products/ps5931/index.html

Similar Messages

NAC is not managing new Cisco Switch 2960S

Hello,
we want to add a Cisco Switch 2960S to the devices, but CAM says he is unable to control that switch.
The switch type Cisco WS-C2960-8TC-L is already running on the CAM.
Is there a OID Update for the 2960S?
Our CAM version is 4.5.1.

Solution:
Use the update on CAM:
-> Device Management -> Clean Access -> Updates -> Update
to get new OIDs for the switches.
This solved the problem. The device was added afterwards successfully.

SFP (Cisco GLC-SX-MM) unknown in cisco switch 2960s

I have cisco switch WS-C2960S-24TS-S with IOS 12.2(55)SE8 C2960S-UNIVERSALK9-M when I connect the SFP Cisco GLC-SX-MM to the interface the switch does not know it .
Switch#sh interfaces gig0/25 status
Port Name Status Vlan Duplex Speed Type
Gi0/25 err-disabled 1 auto auto unknown

Switch(config)#int gigabitEthernet 0/25
Switch(config-if)#sho
Switch(config-if)#shu
Switch(config-if)#shutdown
Switch(config-if)#do sh
*Mar 1 00:08:10.481: %LINK-5-CHANGED: Interface GigabitEthernet0/25, changed state to administratively down ip int br
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES unset up up
FastEthernet0 unassigned YES unset down down
GigabitEthernet0/1 unassigned YES unset down down
GigabitEthernet0/2 unassigned YES unset down down
GigabitEthernet0/3 unassigned YES unset down down
GigabitEthernet0/4 unassigned YES unset down down
GigabitEthernet0/5 unassigned YES unset down down
GigabitEthernet0/6 unassigned YES unset down down
GigabitEthernet0/7 unassigned YES unset down down
GigabitEthernet0/8 unassigned YES unset down down
GigabitEthernet0/9 unassigned YES unset down down
GigabitEthernet0/10 unassigned YES unset down down
GigabitEthernet0/11 unassigned YES unset down down
GigabitEthernet0/12 unassigned YES unset down down
GigabitEthernet0/13 unassigned YES unset down down
GigabitEthernet0/14 unassigned YES unset down down
GigabitEthernet0/15 unassigned YES unset down down
GigabitEthernet0/16 unassigned YES unset down down
GigabitEthernet0/17 unassigned YES unset down down
GigabitEthernet0/18 unassigned YES unset down down
GigabitEthernet0/19 unassigned YES unset down down
GigabitEthernet0/20 unassigned YES unset down down
GigabitEthernet0/21 unassigned YES unset down down
GigabitEthernet0/22 unassigned YES unset down down
GigabitEthernet0/23 unassigned YES unset down down
GigabitEthernet0/24 unassigned YES unset up up
GigabitEthernet0/25 unassigned YES unset administratively down down
GigabitEthernet0/26 unassigned YES unset down down
Switch(config-if)#no shut
Switch(config-if)#
*Mar 1 00:08:30.326: %LINK-3-UPDOWN: Interface GigabitEthernet0/25, changed state to down
Switch(config-if)#
Switch#show ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES unset up down
FastEthernet0 unassigned YES unset down down
GigabitEthernet0/1 unassigned YES unset down down
GigabitEthernet0/2 unassigned YES unset down down
GigabitEthernet0/3 unassigned YES unset down down
GigabitEthernet0/4 unassigned YES unset down down
GigabitEthernet0/5 unassigned YES unset down down
GigabitEthernet0/6 unassigned YES unset down down
GigabitEthernet0/7 unassigned YES unset down down
GigabitEthernet0/8 unassigned YES unset down down
GigabitEthernet0/9 unassigned YES unset down down
GigabitEthernet0/10 unassigned YES unset down down
GigabitEthernet0/11 unassigned YES unset down down
GigabitEthernet0/12 unassigned YES unset down down
GigabitEthernet0/13 unassigned YES unset down down
GigabitEthernet0/14 unassigned YES unset down down
GigabitEthernet0/15 unassigned YES unset down down
GigabitEthernet0/16 unassigned YES unset down down
GigabitEthernet0/17 unassigned YES unset down down
GigabitEthernet0/18 unassigned YES unset down down
GigabitEthernet0/19 unassigned YES unset down down
GigabitEthernet0/20 unassigned YES unset down down
GigabitEthernet0/21 unassigned YES unset down down
GigabitEthernet0/22 unassigned YES unset down down
GigabitEthernet0/23 unassigned YES unset down down
GigabitEthernet0/24 unassigned YES unset down down
GigabitEthernet0/25 unassigned YES unset down down
GigabitEthernet0/26 unassigned YES unset down down
Switch#
Mar 1 00:07:55.508: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
*Mar 1 00:07:55.508: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/25, putting Gi0/25 in err-disable state
*Mar 1 00:08:24.003: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
*Mar 1 00:08:39.144: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
Mar 1 00:24:18.611: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
*Mar 1 00:24:18.611: %PHY-4-UNSUPPORTED_TRANSCEIVER: Unsupported transceiver found in Gi0/25

Cisco switch 2960

whether 2960 is a l2 layer or l3 layer

Cisco introduced Layer 3 switching on the 2960S, 2960G, 2960, and 2975 series switches when running the LAN BASE IOS with version 12.2(55)SE.
But there’s a small catch…it does NOT support RIP, OSPF, EIGRP, BGP, or routed interfaces. It ONLY supports 16 static routes with SVIs.
http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_55_se/configuration/guide/swipstatrout.html
Hope this helps
Sent from Cisco Technical Support iPhone App

Cisco switch 2960s

Hello,
I have a switch which is powers up but does not work. I saw the below logs the I connected to to an interface.
Kindly assist.
POST: Inline Power Controller Tests : Begin
POST: inline power post failed for port 0
POST: inline power post failed for port 1
POST: inline power post failed for port 2
POST: inline power post failed for port 3
POST: inline power post failed for port 4
POST: inline power post failed for port 5
POST: inline power post failed for port 6
POST: inline power post failed for port 7
POST: inline power post failed for port 8
POST: inline power post failed for port 9
POST: inline power post failed for port 10
POST: inline power post failed for port 11
POST: inline power post failed for port 12
POST: inline power post failed for port 13
POST: inline power post failed for port 14
POST: inline power post failed for port 15
POST: inline power post failed for port 16
POST: inline power post failed for port 17
POST: inline power post failed for port 18
POST: inline power post failed for port 19
POST: inline power post failed for port 20
POST: inline power post failed for port 21
POST: inline power post failed for port 22
POST: inline power post failed for port 23
POST: Inline Power Controller Tests : End, Status Failed
POST: Thermal, Fan Tests : Begin
POST: Thermal, Fan Tests : End, Status Passed
POST: PortASIC Stack Port Loopback Tests : Begin
POST: PortASIC Stack Port Loopback Tests : End, Status Passed
POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed
POST: EMAC Loopback Tests : Begin
POST: EMAC Loopback Tests : End, Status Passed
Election Complete
Switch 1 booting as Master
Waiting for Port download...Complete
*Mar 1 00:00:1e Vlan1, changed state to down
*Mar 1 00:01:37.077: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Mar 1 00:02:14.506: %SYS-5-CONFIG_I: Configured from memory by console
*Mar 1 00:02:14.736: %STACKMGR-5-SWITCH_READY: Switch 1 is READY
*Mar 1 00:02:14.736: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state DOWN
*Mar 1 00:02:14.736: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to state DOWN
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/1 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/2 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/3 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/4 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/5 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/6 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/7 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/8 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/9 can't be brought up because it failed POST in Inline Power test.
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/10 can't be broug
*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/11 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/12 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/13 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/14 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/15 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/16 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/17 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/18 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/19 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/20 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/21 can't be broug
*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/22 can't be broug
*Mar 1 00:02:15.025: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/23 can't be broug
*Mar 1 00:02:15.025: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/24 can't be broug
*Mar 1 00:02:15.040: %STACKMGR-5-MASTER_READY: Master Switch 1 is READY
Anim

Hi Frederick,
POST: Inline Power Controller Tests : BeginPOST: inline power post failed for port 0POST: inline power post failed for port 1POST: inline power post failed for port 2POST: inline power post failed for port 3POST: inline power post failed for port 4POST: inline power post failed for port 5POST: inline power post failed for port 6POST: inline power post failed for port 7POST: inline power post failed for port 8POST: inline power post failed for port 9POST: inline power post failed for port 10POST: inline power post failed for port 11POST: inline power post failed for port 12POST: inline power post failed for port 13POST: inline power post failed for port 14POST: inline power post failed for port 15POST: inline power post failed for port 16POST: inline power post failed for port 17POST: inline power post failed for port 18POST: inline power post failed for port 19POST: inline power post failed for port 20POST: inline power post failed for port 21POST: inline power post failed for port 22POST: inline power post failed for port 23POST: Inline Power Controller Tests : End, Status FailedPOST: Thermal, Fan Tests : BeginPOST: Thermal, Fan Tests : End, Status PassedPOST: PortASIC Stack Port Loopback Tests : BeginPOST: PortASIC Stack Port Loopback Tests : End, Status PassedPOST: PortASIC Port Loopback Tests : BeginPOST: PortASIC Port Loopback Tests : End, Status PassedPOST: EMAC Loopback Tests : BeginPOST: EMAC Loopback Tests : End, Status PassedElection CompleteSwitch 1 booting as MasterWaiting for Port download...Complete*Mar 1 00:00:1e Vlan1, changed state to down*Mar 1 00:01:37.077: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan*Mar 1 00:02:14.506: %SYS-5-CONFIG_I: Configured from memory by console*Mar 1 00:02:14.736: %STACKMGR-5-SWITCH_READY: Switch 1 is READY*Mar 1 00:02:14.736: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state DOWN*Mar 1 00:02:14.736: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to state DOWN*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/1 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/2 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/3 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/4 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/5 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/6 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/7 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/8 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/9 can't be brought up because it failed POST in Inline Power test.*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/10 can't be broug*Mar 1 00:02:15.014: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/11 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/12 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/13 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/14 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/15 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/16 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/17 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/18 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/19 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/20 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/21 can't be broug*Mar 1 00:02:15.019: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/22 can't be broug*Mar 1 00:02:15.025: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/23 can't be broug*Mar 1 00:02:15.025: %PLATFORM_ENV-3-ILP_PORT_POST_ERR: Gi1/0/24 can't be broug*Mar 1 00:02:15.040: %STACKMGR-5-MASTER_READY: Master Switch 1 is READY
try no shut on each interface and check it.
If still fails then, Please contact Cisco and try to get the appliance replaced. This swicth is dead, also raise a TAC case.
Reagrds
Dont forget to rate helpful posts.

Collecting information from Cisco switchs using SNMP

Dear All,
I have a wide network with more than 250 sites connected using the DSL. the WAN devices are under the provider responsability and the LAN devices are directly in my responsability. In each site, I have :
1 or 2 Cisco switchs (2960 or 3560), connecting via fibr.
or
Linksys switch connected via ethernet cable
and
cisco 877 router connected to switch
cisco 881G router conected to switch
pc and printers
In order to improve the availibilty of our network, we lauch every day a script from local pc to test connectivity of LAN equipements :
ping to switchs (Vlan 1), ping to ip fa0/0 cisco router1, ip cisco router2, ping to HSRP address (of two router). the resulting ini file will be inserted in a database and exported to excel for analysing.
I'm asking if someone can help in order to implement SNMP and let me know the name of cisco MIB to implement to :
- to have from SNMP information, the result of show cdp nei, show interface status, show ip int brief,...
- to have if wan router LAN interface are up,connected
- others usefuls informations.
Thanks and regards,
AA

Hi,
the basic SNMP config for 2960 and 3560 is:
     snmp-server community <> RO
The configuration for SNMP traps to get alerts from the device if there is for example a failure with a fan is:
          snmp-server enable traps
          snmp-server host <> <>
This enables all traps available with your IOS version. You can the disable not wanted traps by using the "no"-command like this.
Example for dot1x traps:
          no snmp-server enable traps dot1x
With a snmp client you can then do a snmpwalk (or snmp get) without a specific OID to get all the SNMP information from the device:
On a Linux server the following command should work:
     snmpwalk -v 2c -c <> -T <>
-v = use SNMP version 2c
-c = use the community string you configured on the device
-T = output in the dotted decimal format
But be careful, this will be a lot of data output.
Here you will find a docu for configuring SNMP on a Cisco device:
http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf014.html
Sven

Cisco 2960 Series Switch Architecture

Hi all,
I wanted to know if there is a document or an article which describes 2960 series architecture specifically for model WS-C2960-24-S as there is for 2600 series in the following link:
http://www.cisco.com/c/en/us/support/docs/routers/2600-series-multiservice-platforms/23852-2600-architecture-23852.html
Thanks.

Hi,
You should be able to find the information that you need here:
http://www.cisco.com/c/en/us/support/switches/catalyst-2960-24-s-switch/model.html
Thanks,
Jake

Configuring SNMP on Cisco Small Business 300 Series Managed Switch

Please can anyone help me to configure SNMP on Cisco Small Business 300 Series Managed Switch?
Thanks

Hi Anton,
Please remember to enable SNMP service first: Security > TCP/UDP Services.
http://sbkb.cisco.com/CiscoSB/ukp.aspx?vw=1&docid=3b13278d9ef9402a8fef57df6d972078_Enable_SNMP_Service_on_300_Series_Managed_Switches.xml&pid=2&respid=0&snid=2&dispid=0&cpage=search
also you may find useful documents for community configuration etc on our kb server:
http://sbkb.cisco.com/CiscoSB/ukp.aspx?vw=1&docid=183cae2148d445b2a07473ee18c93ffa_SNMP_Communities_Configuration_on_a_300_Series_Managed_Switc.xml&pid=2&respid=0&snid=2&dispid=0&cpage=search
Let us know if you have any problems.
Aleksandra

Plug and Play for Cisco Small Business 300 Series Managed Switch

Good day
what are the Auto-Install options available for the Cisco Small Business 300 Series Managed Switch ?
It would appear there are none, the operating system is not the standard IOS I'm used to.
Would like to use it with Cisco Prime Infrastructure's PnP Gateway capability.
Regards
Pierre

Prime Infrastructure uses and assumes a CNS (Cisco Network Services) agent on the other side when enabling "plug & play". 300/500 Series do not run IOS and does not include a CNS agent, but there is a way to enable auto-configuration. The switches support DHCP Autoconfiguration (using DHCP options 66, 67, and others) whereby they automatically download their config from a TFTP server at boot time. This allows an administrator to put the configs for all the switches on a TFTP server and simply boot a factory-defaulted switch in order to get its config.
Attached is a document showing how this is done.
Hope the information would be of assistance.

Centrally manage all Cisco Switches

I have more than 20 Cisco switches in my office which is basically a soap manufacturing factory. The switches include Cisco 2950, 2960, 3560, 3750 etc. We have routers also which include 2821, 2951 etc. We also have Cisco WLC 2125 and LAP 1262 series. Sometimes all these devices management comes very tough to us.
We need to logon to different devices for troubleshooting/network managment which sometimes becomes very tough to us. So I wonder if there any cisco applications or tools by which we can centrally manage all these devices.
If would be a great help for us if anyone can suggest.

The closest low cost (free) Cisco product to manage most of that would be Cisco Network Assistant (CNA). It'll do fine with your switches and manage at least your 2900 series router.
If I were on a budget I'd use CNA for the switches, add in Cisco Confguration Professional (CCP) for the couple of routers and use the built-in browser-based interface for the WLC (which covers its WAPs as well).
If you want a paid Cisco product to cover it all, you'd have to step up to Cisco Prime Infrastructure at the base licensing level (up to 50 devices). List price for that is about US$5295.
Third party options abound and also range from free open source projects (Nagios, Cacti, RANCID etc.) to full-featured systems such as the SolarWinds products (NPM, NCM, etc.)

Ask the Expert: C-Series Integration with Cisco Unified Computing System Manager

Welcome to the Cisco Support Community Ask the Expert conversation. This conversation is an opportunity to learn and ask questions about Cisco C-Series Integration with Cisco Unified Computing System® Manager (Cisco UCS® Manager) with Cisco experts Vishal Mehta and Manuel Velasco.
Cisco UCS C-Series Rack-Mount Servers are managed by the built-in standalone software, Cisco Integrated Management Controller (Cisco IMC). When a C-Series rack-mount server is integrated with Cisco UCS Manager, the IMC no longer manages the server. Instead you will manage the server using the Cisco UCS Manager GUI or Cisco UCS Manager command-line interface (CLI).
Cisco UCS Manager 2.2 provides three connectivity modes for Cisco UCS C-Series Rack-Mount Server management. The following are the connectivity modes:
Dual-wire management (shared LAN On Motherboard [LOM]): Shared LOM ports on the rack server are used exclusively for carrying management traffic.A separate cable connected to one of the ports on the Payment Card Industry Express (PCIe) card carries the data traffic.
SingleConnect (Sideband): Using Network Controller Sideband Interface (NC-SI), the Cisco UCS Virtual Interface Card 1225 (VIC1225) connects one cable that can carry both data and management traffic.
Direct Connect Mode: Cisco UCS Manager Version 2.2 introduces an additional rack server management mode using direct connection to the Fabric Interconnect.
Vishal Mehta is a customer support engineer for Cisco’s Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in the TAC for the past 3 years with a primary focus on data center technologies such as Cisco Nexus® 5000, Cisco UCS, Cisco Nexus 1000V, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching and service provider.
Manuel Velasco is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past 3 years with a primary focus on data center technologies such as Cisco UCS, Cisco Nexus 1000V, and virtualization. Manuel holds a master’s degree in electrical engineering from California Polytechnic State University (Cal Poly) and CCNA® and VMware VCP certifications. Remember to use the rating system to let Vishal and Manuel know if you have received an adequate response.
Because of the volume expected during this event, our experts might not be able to answer every question. Remember that you can continue the conversation in the Data Center, under subcommunity, Unified Computing, shortly after the event. This event lasts through May 23, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Sebastian,
The different modes of connecting C-Series with UCSM come into play depending on the type of infrastructure you already have along with C-Series and NIC model.
Cisco UCS C-Series Rack-Mount Servers are managed by the built-in standalone software, Cisco Integrated Management Controller (CIMC) .
Powerful features provided by Cisco UCS Manager can be leveraged to manage C-Series server by integrating C-Series Rack-Mount Server with UCSM.
This not only gives you rich-feature set but also one management plane to operate UCS-B Series Chassis and UCS-C Series Rack Server.
You will manage the server using the Cisco UCS Manager GUI or Cisco UCS Manager CLI.
Cisco UCS Manager 2.2 provides three connectivity modes for Cisco UCS C-Series Rack-Mount Server management.
The following are the connectivity modes:
• Dual-wire Management (Shared LOM):
Shared LAN on Motherboard (LOM) ports on the rack server are used exclusively for carrying management traffic. A separate cable connected to one of the ports on the PCIe card carries the data traffic. Using two separate cables for managing data traffic and management traffic is also referred to as dual-wire management.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c-series_integration/ucsm2-2/b_C-Series-Integration_UCSM2-2/b_C-Series-Integration_UCSM2-2_chapter_0100.html
This mode is recommended when you have C-Server which does not have or cannot support VIC 1225 card (such C-200 server)
• SingleConnect (Sideband):
Using Network Controller Sideband Interface (NC-SI), Cisco UCS VIC1225 Virtual Interface Card (VIC) connects one cable that can carry both data traffic and management traffic.
This feature is referred to as SingleConnect.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c-series_integration/ucsm2-2/b_C-Series-Integration_UCSM2-2/b_C-Series-Integration_UCSM2-2_chapter_011.html
This most recommended Integration model when using FEX and VIC 1225 card
• Direct Connect Mode:
Cisco UCS Manager release version 2.2 introduces an additional rack server management mode using direct connection to the Fabric Interconnect.
This mode will eliminate the need for FEX module as Servers are directly plugged into the base ports of Fabric Interconnect
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c-series_integration/ucsm2-2/b_C-Series-Integration_UCSM2-2/b_C-Series-Integration_UCSM2-2_chapter_0110.html
Please let us know if you need more information. Thank you!
Thanks,
Vishal

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Increasing TFTP block size for 2960 series switches

I have read that some Cisco components can increase the default TFTP block size to values greater than 512 bytes by using the command -
ip tftp blocksize xxxx
This doesn't seem to be available on Cisco 2960 series switches. Is there a way to do this with the 2960's?

I have moved a WS-C2960-24LC-S running LanLite to 12.2(55)SE9 - the current end of the line for this switch - and indeed the command is not present. Sooo....this appears to be a limitation of LanLite.
My predecessor implemented about 70 switches with LanLite. I put a stop to this about a year ago but it is going to take some time to flush them out of the inventory.
Thanks for your response.

Cisco 2960 series mismatch

i have a switch, that shows next
Switch Ports Model SW Version SW Image
* 1 26 WS-C2960S-24TS-S 12.2(55)SE5 C2960S-UNIVERSALK9-M
but!
WS-C2960S-24TS-S <- what does this meen?
what i ask about:
catalist 2960 have 2960-S-series and simple 2960 (not S), and i hav'nt found WS-C2960 with S-suffix at http://www.cisco.com/c/en/us/products/switches/catalyst-2960-series-switches/models-comparison.html
there is WS-* only without *S.
what the device vertion is real and where can i find info about this device?

I found the following info:
"WS-C2960S-24TS-L is Lan Lite Switch.but WS-C2960S-24TS-S is the Lan Base. The obvious differences is hardware differences.The LAN Base owns advanced Layer 2 and mainly is designed for large enterprise. However, The LAN Lite offers entry-level L2 features ,which aims at mid market deployments."
http://www.router-switch.com/ws-c2960s-24ts-s-p-1518.html

Management port in Cisco Switches (are they really physical port)

Hi all,
I have been taught to console into my cisco switch for configurations through console cable + putty (serial terminal).
Then I have been taught to configure a management ip and gateway on the cisco switch.
Switch# conf t
Switch(config)# interface vlan 1
Switch(config-if)# ip address 192.168.1.11 255.255.255.0
Switch(config-if)# no shut
Switch(config-if)# exit
Switch(config)# ip default-gateway 192.168.1.1
All the while, i thought this is the way to remote in to the switch via putty/telnet through the network to configure the switch, until i saw the picture below (cisco catalyst 2960)
=======================================
There is a physical port call ethernet management port. What is it ? What is the difference between this port and the earlier example of setting a management ip in VLAN 1 ?
If i set an IP on this particular interface and I ssh in, will i see the same screen/display/console from the earlier example in which i set a management ip in VLAN1 and I ssh in ?
Regards,
Noob

Hi Leo,
Sorry if you find it hard to explain to me.
I have understood to think of the ethernet management port as a separate entity from the original switch.
Maybe with the help of the diagram below, can you let me know if i have understood correctly ?
*please assume connected port is a management port separated from the normal switch ports
q1) does the ethernet management port need to be connected to another switch ?
I have thought of it as a device on the network and it is mentioned by you previously that it will be connected to a switch
"he traffic goes up the cable connected to the Management port and up a switch. Now that switch holds all the information because it is a switch. "
q2) In the current setup then, terminal B will be able to access the management port - am i right ?
q3) you mentioned that the management port is not able to set any gateway, (which is the router fe0/5 - 192.168.0.3 in my illustration), in that case do you mean that terminal A will not be able to access the management port remotely and it can only be accessible locally ?
Please do correct me if my understanding is wrong.
Thank you so much for your advices.
Regards,
Noob

Cisco Switches (2960 Series) Management

Similar Messages

Maybe you are looking for