Search this Blog

Monday, July 25, 2011

2811 Router with 4 port switch module L3 question

We would like to put an IP address on the interfaces of the 4-port switch in the router. We want to be able to configure it like below - int fa0/0/0 ip address 216.90.191.56 255.255.xxx.xxx It keeps coming up with it is only a layer 2 port. Can we change this port to layer 3?

The 4 port hwic do route you just cannot assign an ip address directly to the port. Create a layer 2 vlan and the corresponding layer 3 SVI , which you assign your ip address to . Then assign the hwic switchport into that vlan . Just about the same as a routed port.
router# vlan database vlan 2 exit conf t interface vlan 2 ip ADDRESS 192.232.168.1 255.255.255.0 no shut exit int fast2/1 ---> hwic port# switchport acess vlan 2 .

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Does VSS have an advantage over HSRP, redudancy?


Does VSS have more redudancy than HSRP because VSS has both distribution switches active instead of passive and active like HSRP?

VSS differnt from HSRP interms of mechanism and also VSS is not a protocol.

The most important thing here is although both they archive many to one vitalization but with HSRP you have the topology works in active/Standby for both control plan and data/forwarding plan

However with VSS you will have control plane works in active/standby ( manage routing, ARP and config through the Active VSS peer ) however from forwarding plane both devices/uplinks are in forwarding so you will have all you links forwarding which is not achievable using HSRP ( unless you are using cisco Nexus Switches )

The decision based on the requirements - size and amount of traffic and budget as well but interns which one better if you can afford it i would say VSS

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Thursday, July 21, 2011

What is the maximium amount of port channnels on WS-C3750G-24T-S?

We currently connect all of my VM hosts to stacks of cisco WS-C3750G-24T-S (24 port 3750G switches) . All of the physical interfaces on the VM hosts participate in port-channels that live on the cisco 3750 stacks. The port channel count of 48 on the 3750 stack limits me due to the fact that each host has three port channels that are specific to that host (prod, vmotion & future use). Does cisco have plans on increasing the port channel count in future a future IOS release for the cisco WS-C3750-24T-S (24 port 3750G switch) as well as other devices?

Max port channels a 3750 Switch can have is 48.
However since your switch has just 24 ports, you can have 24 portchannels max. (Additonally, out of 1 to 48 port channel numbers, you can choose only 24 numbers...i.e., total count of port channels can be 24 only).


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Tuesday, July 19, 2011

VSS configuration on 2 6509-E chassis question

Currently we are running VSS on 2 6509-E chassis. Both chassis have identical hardware:
VS-S720-10G-3C (1 per chassis)
WS-X6708-10G-3C (1 per chassis)
other line modules
s72033-adventerprisek9_wan-vz.122-33.SXI6.bin

The VSL links use 1 TenGig iface on the supervisor, and 1 TenGig iface on the 6708 linecard on each chassis.
We also configured dual-active detection (fast-hello).

We don't like the 1 supervisor in both chassis. If the sup fails, the VSS setup is useless.
My question: can we easily add (and configure the 2nd VSL link on the new supervisors) a supervisor in each chassis withouth having to convert the VSS system to standalone mode?

Can we convert from a 1 supervisor/chassis VSS setup (as configured now) to a 2 sup/chassis VSS setup without converting to stand-alone mode to configure the aditional VSL links... (as this will cause serious downtime).

Yes, you can add the second Supervisor without going back to standalone mode.

However, as long as everything is dual-homed to the VSS, the loss of a single Supervisor should have only sub-second impact on traffic as it switches to the remaining switch in the Multi-chassis EtherChannels. MOre information about Quad Supervisor Uplink Forwarding can be found here.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Tuesday, July 12, 2011

CISCO Catalyst 6500 VSS failure software upgrade


We have tried to upgrade 6500 VSS system from 12.33.SXI3 to 12.33.SXI6
Installed modules on one switch and the same hardware config in the another switch:
#sh module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SADXXXXXXXX
2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SADXXXXXXXX
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SADXXXXXXXX
4 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SADXXXXXXXX
5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G SALXXXXXXXXX
7 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SADXXXXXXXX
8 16 CEF720 16 port 10GE WS-X6716-10GE SALXXXXXXXXX
9 6 Firewall Module WS-SVC-FWM-1 SADXXXXXXXX

Supervisor is starting correctly, but in short period I got this message in the log file:
Jul 7 2011 01:13:34.983 EET: %XDR-3-CLIENTISSU_PUSHFAIL: Attempting to push send XDR message (hqf ipc) to slots 21/0
37/0 39/0-40/0 21/1 (0x2001A000200000) via XDR client CEF push failed due to invalid slot : ios-base : (PID=16406, TID=3) : -Traceback=(s72033_rp-advente
rprisek9_wan-8-dso-b.so+0x3034A4) ([30:-9]4+0x2A6328) ([40:0]+0x2A6660) ([40:0]+0x2A66C0) ([30:-9]6+0x3CCEE8) ([40:0]+0x3CDF78) ([40:0]+0x3CE0AC) ([40:0]+
0x3CE91C) ([40:0]+0x3CEAF0) ([30:-9]4+0x45B2E0) ([40:0]+0x2A73A0) ([40:0]+0x2A74B4) ([30:-9]11+0x3D2400) ([30:-9]8+0x2F506C) ([30:-9]7+0x39E570) ([30:-9]1
1+0x3D08DC)

The error message you saw is generated when an XDR client tries to send a message to two or more slots running different versions of images and indicates that the XDR message has been dropped. This is caused by a known software defect CSCsu67841 which is duplicated to CSCsx76168. This is only fixed in 12.2(33)SXI4, therefore you’ll encounter this because you’re running SXI3.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Friday, July 1, 2011

Cisco 6513 OSM-2OC48/1DPT-SL issue error


My module OSM-2OC48/1DPT-SL on Cisco 6513 issue error any here is my message.
%CONST_DIAG-SP-6-HM_MESSAGE: High traffic/CPU util seen on Module 7 [SP=8%,RP=98%,Traffic=0%]

The Switch processor(SP) sends a Health Monitor (HM) ping packet to the RP in every 15 seconds time interval. On receipt of this ping packet, the RP returns the same packet back to the SP. If the same ping packet is received then this process recurs again 15 seconds later. In the event that either the SP or the RP's CPU utilization exceeds 80%,
this message is printed out and the sending of ping packets are ceased temporarily until CPU drops below 80%.


If you are seeing this message consistently in the logs use sh process cpu on both RP and SP (remote login command) when this occurs. Also check sh ip traffic and sh ip interface for incrementing drops.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.
 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */