2014年3月4日星期二

Receiving error - Can't find applicable device package - in CiscoView

 I have CiscoWorks LMS 2.6 with CiscoView 6.1.5 & with version 4.0 of the WS-C3560X-48T-L   device package. For some reaseon I'm getting the following when I try to bring up a 3560' in CiscoView's ChassisView

Message
Can't find applicable device package for 10.20.2.11.

Cause
Device package for this device type is not installed or device support for this device type might not be available or you are attempting to open a component inside a device.

Action
Please install a device package for the device type or open the parent device to manage the component.
--------------------------------

  Here is a show ver of one of the switches that chassisview can not bring up ...

C3560 Software (C3560-IPBASEK9-M), Version 12.2(40)SE,
cisco WS-C3560-24PS (PowerPC405) processor (revision Q0)

Yes, you can copy the WS-C3560X-48T-S  .zip package from the PSU location to the active CV location.  Then restart dmgtd.


2014年2月23日星期日

Cisco Catalyst 3750-E

In the two previous posts I covered how to create multiple VLANs, trunk those VLANs between multiple stackable Avaya Ethernet Routing Switches utilizing Multi-Link Trunking and how to create Layer 3 IP interfaces to be used for routing IP packets between those VLANs.

In this post I thought I would expand the network topology of my previous two posts to include a Cisco Catalyst WS-C3750X-12S-S   . I’ll specifically cover how to trunk (bridge) multiple VLANs between a stackable Avaya Ethernet Routing Switch and the Cisco Catalyst 3750-E and how to configure multiple interfaces in a Link Aggregation Group (LAG) utilizing LACP similar to Avaya’s proprietary MLT feature.

Avaya Ethernet Routing Switch 4548

Avaya Ethernet Routing Switch 4548 – Show Commands

4548GT-PWR#show lacp port 45,46

Admin Oper         Trunk Partner

Port Priority Lacp    A/I Timeout Key   Key   AggrId Id    Port    Status

---- -------- ------- --- ------- ----- ----- ------ ----- ------- ------

45   32768    Active  A   Short   10    12298 8224   32    302     Active

46   32768    Active  A   Short   10    12298 8224   32    303     Active

4548GT-PWR#show mac-address-table

Mac Address Table Aging Time: 300

Number of addresses: 26

   MAC Address    Vid  Source         MAC Address    Vid  Source

00-02-B3-CB-77-A2    1 Port:19     00-04-61-9E-46-7E    1 Port:21

00-0C-29-64-33-F9    1 Port:19     00-0C-29-A5-CB-54    1 Port:19

00-0F-20-95-38-D5    1 Port:11     00-18-01-EA-F4-45    1 Port: 1

00-1C-11-6B-DC-6B    1 Port: 1     00-1C-11-6D-15-27    1 Port: 1

00-1C-11-6D-15-DC    1 Port: 1     00-1E-7E-7C-2C-00    1

00-1E-7E-7C-2C-40    1             00-1F-0A-CE-BC-01    1 Trunk:1

00-1F-0A-CE-BC-40    1 Trunk:1     00-1F-D0-D0-BE-2D    1 Port:17

00-23-EE-96-AA-21    1 Port: 1     00-24-B5-F6-94-02    1 Trunk:1

00-64-40-CF-4D-AD    1 Trunk:32    00-64-40-CF-4D-AE    1 Trunk:32

00-64-40-CF-4D-C0    1 Trunk:32    00-0A-E4-76-9C-C8    2 Port:44

00-24-DC-DF-0D-08    2 Port:43     00-A0-F8-5E-CE-BC    2 Port:39

00-1F-0A-CE-BC-41  100 Trunk:1     00-24-7F-99-84-70  100 Port:25

00-64-40-CF-4D-AD  100 Trunk:32    00-1E-CA-F3-1D-B4  200 Port:26

00-1F-0A-CE-BC-43  200 Trunk:1     00-64-40-CF-4D-AD  200 Trunk:32

4548GT-PWR#show mlt

Id Name             Members                Bpdu   Mode           Status  Type

-- ---------------- ---------------------- ------ -------------- ------- ------

1  MLT_to_ERS5520   47-48                  All    Basic          Enabled Trunk

2  Trunk #2         NONE                   All    Basic          Disabled

3  Trunk #3         NONE                   All    Basic          Disabled

4  Trunk #4         NONE                   All    Basic          Disabled

5  Trunk #5         NONE                   All    Basic          Disabled

6  Trunk #6         NONE                   All    Basic          Disabled

7  Trunk #7         NONE                   All    Basic          Disabled

8  Trunk #8         NONE                   All    Basic          Disabled

9  Trunk #9         NONE                   All    Basic          Disabled

10 Trunk #10        NONE                   All    Basic          Disabled

11 Trunk #11        NONE                   All    Basic          Disabled

12 Trunk #12        NONE                   All    Basic          Disabled

13 Trunk #13        NONE                   All    Basic          Disabled

14 Trunk #14        NONE                   All    Basic          Disabled

15 Trunk #15        NONE                   All    Basic          Disabled

16 Trunk #16        NONE                   All    Basic          Disabled

17 Trunk #17        NONE                   All    Basic          Disabled

18 Trunk #18        NONE                   All    Basic          Disabled

19 Trunk #19        NONE                   All    Basic          Disabled

20 Trunk #20        NONE                   All    Basic          Disabled

21 Trunk #21        NONE                   All    Basic          Disabled

22 Trunk #22        NONE                   All    Basic          Disabled

23 Trunk #23        NONE                   All    Basic          Disabled

24 Trunk #24        NONE                   All    Basic          Disabled

25 Trunk #25        NONE                   All    Basic          Disabled

26 Trunk #26        NONE                   All    Basic          Disabled

27 Trunk #27        NONE                   All    Basic          Disabled

28 Trunk #28        NONE                   All    Basic          Disabled

29 Trunk #29        NONE                   All    Basic          Disabled

30 Trunk #30        NONE                   All    Basic          Disabled

31 Trunk #31        NONE                   All    Basic          Disabled

32 Trunk #32        45-46                  Single DynLag/Basic   Enabled Trunk


You might be looking at the output above and asking yourself what’s “Trunk 32″? Let me provide some quick background. You can have a total of 32 MLT/LAG trunks on a stackable Avaya Ethernet Routing Switch. When you create LACP trunks the switch automatically creates a LAG in the MLT table dynamically from the bottom up. While in the previous post I created “Trunk 1″ by trunking ports 47 and 48 together (see above), in this post I’ve created an LACP trunk on ports 45 and 46 which will be reported it the WS-C3750V2-48PS-S   switch as “Trunk 32″. You can also see it in the MAC/FDB table above.

2014年2月20日星期四

3750s stack or Catalyst 6500?

i'm working in a government health network and we actually have a Cisco Catalyst 4503 as a Core Switch with a bunch of 2960Gs and 2950, etc. My question is regarding the best solution to have for having the Core Switch to change.

Scenario 1: 4x Catalyst 3750 24 Ports and 1x WS-C3750V2-24PS-S    12 ports all 5 stacked

Scenario 2: 1x Catalyst 6500 48 ports and another one 24 ports SFPs

I think both scenarios would be approximatly the same cost or around it, but it's not a matter of money. I would like to know what would be the best solution for us for scalability, fault tolerance, network management, etc.

The only flaw that I see going for 6500 is that it doesn't give me redundancy in terms of chassis. If you are planning to go for two supervisors in the chassis, it will be a better option.

1) You can add/remove modules from 6500 as & when you want without having to pay for any other switch, I assume that the modules would be cheaper than buyig a whole new switch.

2) It gives you more backplane speed.

3) Hardware forwarding.

4) Most of routing & other functions would be handled in hardware.

Overall, 6500 is much more advanced than 3750.


So, I would go for 6500. For more details, I would suggest going through the datasheet of both these WS-C3750X-24P-S    switches.

2014年2月17日星期一

cisco 3750 high cpu

We have a cisco WS-C3750X-24T-L    that sometimes shows high cpu.

Please see details below. When cpu was running high, we noticed

2 process that seems to be the culprit. One is VMATM Callback and one is IP Input.

What is VMATM? Can't seem to find much documentation with it.

Also, IP Input seems to be well documented but I'm wondering how it ties into VMATM if it does?

CPU utilization for five seconds: 99%/29%; one minute: 99%; five minutes: 90%

CPU utilization for five seconds: 73%/28%; one minute: 76%; five minutes: 77%

PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process

237          49        53        924  0.00%  0.00%  0.00%   0 VMATM Callback<----------normal usage

237      119304      3710      32157 31.74% 27.42% 17.27%   0 VMATM Callback

198      541972   1524333        355  1.11%  0.55%  0.41%   0 IP Input <------------------normal usage

198    21565303  54238166        397 25.30% 25.51% 25.52%   0 IP Input

Version:

c3750e-universalk9npe-mz.122-55.SE3.bin

CSCtj95182 - High CPU on 3750 when network scanner is run

CSCtf23298 - tacacs-server host ' ' single-connection causes high CPU utilization

 This 'VMATM' process mainly takes care of the removing the

addresses learnt on an interface when the interface goes down.


There are couple of things to be check on this kindly open a TAC case with cisco so that we provide you in depth WS-C3750X-24T-S   analysis on the same

2014年2月13日星期四

OSPF on 3750 with IP Base?

Just doing a quick sanity check on my decision before I purchase but have found some conflicting information that I do with help clarifying!

I'm purchasing a WS-C3750X-24T-L   and need to run OSPF, can I do this with IP Base? The Cisco product page would appear to say Yes, I quote:

"Software versions

LAN Base: Enterprise Access Layer 2 Switching

IP Base: Enterprise Access Layer 3 Switching, including OSPF (Open Shortest Path First) for routed access

IP Services: Advanced Layer 3 Switching (IPv4 and IPv6) "

But from everything else I've read on these forums only static routing is available in IP Base along with RIP, can anyone shed some light on this? By Routed Access does it simply mean OSPF can be used but only as a Stub area (much like EIGRP with IP Base?)


Newly released IOS version 12.2(55)SE WS-C3750X-24T-S   support OSPF v1 ONLY.

2014年2月12日星期三

problem getting iOS 15.0.2 to run on 3750-x 48ps-s

Trying to get the 10Gbps service module to be recognised requires V15 according to cisco  WS-C3750V2-24PS-S  docs

Upgrading from V12.2 55 (or .58) fails on some switches I have tried

Process fails and I finish up at the switch: prompt

I can recover....

The switch can be regressed back to v12.2.55 or .58

But I can't get all of them up to v15

I have tried 5 to date

Same methods producing different results

2 worked

3 failed

All our problematic switches are 48 ports ones, we have some 24 port ones but they're newer and aren't affected. Our testing of the affected switches suggests it's related to their age/hardware revision:

VO1 – fail to load image, get stuck in continual reboot, eventually fail to ROMMON.

VO2 serial number beginning FDO15 – freeze whilst loading image.


VO2 serial number WS-C3750X-24P-S    beginning FDO16 and up – work fine.

2014年1月1日星期三

add swich to stack (cisco 3750)

I want to add 2 switches to my stack of 2.
Switch 1 is the top switch in rack and has a priority of 15
Switch WS-C3750X-24P-S   2 the is second switch in rack and has priority of 14
How can I configure the stack (provision configuration) so that the 3rd switch  in rack will get switch number 3 and the 4th switch in rack gets number 4
All swiches are exact same module

    Just do one-by-one method with following configuration only from the stack master.

Switch(config)# switch 3 provision switch_PID - put your 3rd switch into stack.

Verify the status of the provisioned switch. For stack-member-number, enter the same number as in Step 1.

Switch(config)# switch 4 provision switch_PID - put your 4th switch into stack.

Verify and save the config.

Note - switch_PID:
For type, enter the model number of a supported switch that is listed in the command-line help strings.

change the stack member number by using the switch <current-stack-member-number>  renumber <new-stack-member-number> global configuration command,

show swithc will show the current swithc number and priority
  3750-Stk>show switch
                                                   Current
    Switch#  Role      Mac Address     Priority     State
    --------------------------------------------------------
     1       Slave     0016.4748.dc80     1         Ready
    *2       Master    0016.9d59.db00     5         Ready

the new number goes into effect after that stack member resets (or after you use the reload slot stack-member-number privileged EXEC command) and only if that number is not already assigned to any other members in the stack.

A higher priority value for a stack member increases its likelihood to be elected stack master and to retain its stack member number. The priority value can be 1 to 15. The default priority value is 1. You can display the stack member priority value with the show switch user EXEC mode command.

    3750-Stk>show switch
                                                   Current
    Switch#  Role      Mac Address     Priority     State
    --------------------------------------------------------
     1       Slave     0016.4748.dc80     1         Ready
    *2       Master    0016.9d59.db00     5         Ready

Cisco recommends that you assign the highest priority value to the switch that you prefer to be the stack master. This ensures that the switch is re-elected as stack master if a re-election occurs.

How do you change the priority value?

    From the global configuration mode, issue the command switch stack-member-number priority new-priority-value .

    From the bootloader switch: prompt, issue the command set SWITCH_PRIORITY new-priority-value .

Even though the priority value applies immediately to the member, it will not affect the status of the current stack master. New priority value will play a role in the next stack-master election.

Yes the switches will retain their numbers even if you set different priorities.

The priority sets which switch in the stack becomes the master.  The number is just that - the number of the switch WS-C3750X-24P-L    in the stack.  Once it's set the number won't change unless you change it in the config.