Cisco Catalyst Switches – Adding Licenses

Posted on 17/11/2015 by Migrated

KB ID 0001012

Problem

I had a load of Cisco Catalyst 3560 switches that needed ‘ipbase’ licenses adding to them today. I’ve messed about with plenty of ASA license upgrades before, but not switches.

Solution

1. First thing you need is a Cisco PAK, this may be in an email or turn up in a cardboard envelope.

2. Go to http://www.cisco.com/go/license and log in (if you don’t already have a Cisco CCO account you can create one for free). Enter your PAK and select ‘fulfil’.

3. Select ‘All Quantities’ > Next.

4. Enter your product ID and serial number (see below).

To locate your Product ID (PID), and serial number (SN), on the switch issue a ‘show license udi’ command.

[box]

Petes-Switch#show license udi
Device#   PID                   SN              UDI
-----------------------------------------------------------------------------
*0        WS-C3560X-24T-L       FDO1818X123     WS-C3560X-24T-L:FDO1818X123

Petes-Switch#

[/box]

5. Accept the agreement > ensure your email address is correct > Submit.

6. Select ‘Download’ to get the license straight away (it will get emailed to you shortly).

Note: If it does not turn up in your email, check your junk email folder, I’m sure Microsoft Outlook does this on purpose!

7. You will have a file with a big long name and a .lic extension. If you want you can copy this onto the switch via TFTP, but let’s keep things simple and use a FAT32 formatted USB drive.

8. Before we start let’s check the license on the switch. I’m running my ipbase license on an evaluation, this is what we are going to add a permanent license for.

[box]

Petes-Switch#show license
Index 1 Feature: ipservices
        Period left: 8  weeks 4  days
        License Type: Evaluation
        License State: Active, Not in Use, EULA not accepted
        License Priority: None
        License Count: Non-Counted

Index 2 Feature: ipbase
        Period left: 7  weeks 5  days
        License Type: Evaluation
        License State: Active, In Use
        License Priority: Low
        License Count: Non-Counted

Index 3 Feature: lanbase
        Period left: Life time
        License Type: Permanent
        License State: Active, Not in Use
        License Priority: Medium
        License Count: Non-Counted


Petes-Switch#

[/box]

9. Pop in the USB key with our .lic file on it.

10. Then copy the .lic file to the switches flash memory.

[box]

Mar 30 04:13:18.466: %USBFLASH-5-CHANGE: usbflash0 has been inserted!
Petes-Switch#copy usbflash0: flash:
Source filename []? FDO1818X123_201410200338212345.lic
Destination filename [FDO1818X123_201410200338212345.lic]? {Enter}
Copy in progress...C
1152 bytes copied in 0.041 secs (28098 bytes/sec)
Petes-Switch#

[/box]

11. Install the new license.

[box]

Petes-Switch#license install flash:/FDO1818X123_2014102003382212345.lic
Installing licenses from "flash:/FDO1818X123_2014102003382212345.lic"
Installing...Feature:ipbase...Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install

Petes-Switch#
Mar 30 04:19:35.643: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c3560x 
Next reboot level = ipbase and

License = ipbase
Mar 30 04:19:36.146: %LICENSE-6-INSTALL: Feature ipbase 1.0 was installed in this device. 
UDI=WS-C3560X-24T-L:FDO1818X123;

StoreIndex=1:Primary License Storage
Petes-Switch#

[/box]

12. The license wont take effect until you reload the switch.

[box]

Petes-Switch#write mem
Building configuration...
[OK]
Petes-Switch#reload
Proceed with reload? [confirm]{Enter}

Mar 30 04:20:43.104: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload command.

[/box]

13.Post reboot, check and the license should now be permanent.

[box]

Petes-Switch#show license
Index 1 Feature: ipservices
        Period left: 8  weeks 4  days
        License Type: Evaluation
        License State: Active, Not in Use, EULA not accepted
        License Priority: None
        License Count: Non-Counted

Index 2 Feature: ipbase
        Period left: Life time
        License Type: Permanent
        License State: Active, In Use
        License Priority: Medium
        License Count: Non-Counted

Index 3 Feature: lanbase
        Period left: Life time
        License Type: Permanent
        License State: Active, Not in Use
        License Priority: Medium
        License Count: Non-Counted


Petes-Switch#

[/box]

Windows – Getting Drivers for ‘Unknown Device’ or ‘Base System Device’

Posted on 17/11/2015 by Migrated

KB ID 0000699

Problem

There’s nothing more annoying, you have just rebuilt your PC and you are missing some drivers. Everything appears to be working but there’s one (or more) devices in Device Manager with a yellow exclamation mark over them called ‘Unknown Device’ or ‘Base System Device”.

Solution

This solution is not a ‘Fix All’ for all situations, but it will point you in the right direction. Even if you can find out that the device is an “Intel chip called EL-XYZ” for example, some Google searching will get you the correct driver when you know what you are looking for.

1. So in device manager (Windows Key+R > devmgmt.msc{enter}). Here are two devices I don’t have drivers for, open the properties for the first one and select ‘Details’ > Change the property to ‘Hardware ID’.

2. Locate the Vendor ID (looks like VEN_{this number}) > Locate the Device ID (looks like DEV_{this number}) > Write them down.

3. Go to PCIDatabase, and search for either, (though the Device ID is your best bet).

4. Progress! Now we know it’s a JMicron Card Reader that needs a driver > There is a link to click as well.

5. Here we are lucky, it’s giving us the direct download form the vendors FTP site, you may not be as lucky, but a Google Search for “{device name} + {version of Windows} + {x64 or x32 bit} + {Driver}” should get you there.

How to Tell if Windows is 32 or 64 bit

6. I went to that FTP site, and after a bit of clicking about I downloaded the newest driver, (I scientifically picked the one with the biggest number!) And installed it.

. Device Working.

6. The second device didn’t have a handy link, but it told me it was a device made by “Validity” so I guessed it was the finger print reader on my laptop, and got the driver straight from Hewlett Packards site.

Drivers I’ve Had to Look For

I will add any odd ones that have been difficult to find below, (Note: There are literally millions of drivers, these are just the ones I’ve ever had to search for.)

PCIVEN_197B&DEV_2391&SUBSYS_1619103C&REV_3

USBVID_138A&PID_003C&REV_0086

If you want me to add any you’ve add a nightmare locating, click the contact link below and send me the details.

PowerShell – List All Domain Users and Their Last Logon Time

Posted on 17/11/2015 by Migrated

KB ID 0000752

Problem

In the past I’ve looked at third party tools to do this but what if you wanted to use PowerShell?

Solution

Heres’ a cool solution that might interest you also

Updating Domain Computer Objects with User and Machine Information

1. On your server paste the following script into Notepad;

[box]

$NumDays = 0
 $LogDir = ".Users-Last-Logon.csv"

$currentDate = [System.DateTime]::Now
 $currentDateUtc = $currentDate.ToUniversalTime()
 $lltstamplimit = $currentDateUtc.AddDays(- $NumDays)
 $lltIntLimit = $lltstampLimit.ToFileTime()
 $adobjroot = [adsi]''
 $objstalesearcher = New-Object System.DirectoryServices.DirectorySearcher($adobjroot)
 $objstalesearcher.filter = "(&(objectCategory=person)(objectClass=user)(lastLogonTimeStamp<=" + $lltIntLimit + "))"

$users = $objstalesearcher.findall() | select `
 @{e={$_.properties.cn};n='Display Name'},`
 @{e={$_.properties.samaccountname};n='Username'},`
 @{e={[datetime]::FromFileTimeUtc([int64]$_.properties.lastlogontimestamp[0])};n='Last Logon'},`
 @{e={[string]$adspath=$_.properties.adspath;$account=[ADSI]$adspath;$account.psbase.invokeget('AccountDisabled')};n='Account Is Disabled'}

$users | Export-CSV -NoType $LogDir

[/box]

File > Save As > Save the file as Users-Last-Logon.ps1 > Change the file type to ‘All Files’ >Save it in C:WindowsSystem32.

2. Open PowerShell, and execute the following commands;

[box]

cd c:WindowsSystem32
 ./Users-Last-Logon.ps1

[/box]

3. Navigate to c:WindowsSystem32 and locate the Users-Last-Logon.csv file.

4. Open the file in Excel, and you can sort the ‘Last Logon’ column, to get the users in the correct order.

Update 24/05/13

Email form reader ‘Simon’

I read your article “PowerShell – List All Domain Users and Their Last Logon Time” and it helped me out a lot. Thank your very much for this.

May i suggest to add a filter option on the script, in order to get more results. Currently the script limits the result to 1000. In my Environment there are more users than that.

I added $objstalesearcher.PageSize=4000 to the script, and i got all the users from my bomain.

Again, thank you very much for the script you provided. saved me tons of time !

Exchange 2003 – NDR ‘This message is too large to send.’

Posted on 17/11/2015 by Migrated

KB ID 0000620

Problem

An NDR is received by someone trying to send you an email that is too big, this is an example of what they get sent back to them.

Delivery has failed to these recipients or groups:

Recipients Email Address
This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.

Diagnostic information for administrators:

Generating server: receiving server name

recipient@your-domain.com
#< #5.2.3> #SMTP#

Original message headers:

From: "Sender Name" <sender@senders-domain.com>
To: "IMB Recipient 1" <connectorname@recipient-domain.com>
Message-ID: <message-ID@your-local-domain.local>
Subject: RE: Original Subject Line
MIME-Version: 1.0
Content-Type: text/plain

Solution

The client who logged this call to me was running SBS 2003, so the error was being generated by Exchange 2003. By default Exchange 2003 has a 10 MB limit on incoming mail messages, I just needed to raise the limit.

On the Exchange Server > Start > All Programs > Microsoft Exchange > System Manager > Locate Message Delivery > Properties > Defaults > Set the ‘Receiving message size’ accordingly > Apply > OK.

Note: The limits are here for a reason! Be careful raising them too high, can result in your mail stores growing very quickly.

Windows – ‘The directory service has exhausted the pool of relative identifiers’

Posted on 17/11/2015 by Migrated

KB ID 0000797

Problem

I got this error when attempting to bulk create users with CSVDE (see below). But you may simply see it when trying to create a user, or other AD object.

Unwilling To Perform
The server side error is “The directory service has exhausted the pool of relative identifiers.”

Solution

Well that is a scary looking error! Firstly make sure you can see all your FSMO role servers.

Locate your FSMO Role Servers

In my case, I tracked this down to an old DC that has been removed from the domain but was still referenced in DNS. Open your domain forward lookup zone, look in the _tcp container, for any SRV references to old/removed domain controllers and simply delete them.

Setup an HP 1800-24G (J9028B) Switch

Posted on 17/11/2015 by Migrated

KB ID 0000800

Problem

Essentially you can unbox this switch, plug it in and it will do what you want (unless you have VLANS, or trunks (port-channels)). Which is what my client had done, but I needed to get on the web console and have a look at what was going on, and there is NO CONSOLE socket on this unit at all.

Solution

1. Don’t bother looking in DHCP, it’s NOT set to DHCP by default. From the factory the switch will have the following IP address; 192.168.2.10 (255.255.255.0). So put yourself on the same network segment and connect to the switch via a normal network cable.

Note: Start > Run > ncpa.cpl will get you there.

2. Now open a browser window and connect to https://192.168.2.10 by default the password will be blank.

3. To change the IP address, navigate to System > IP Address > Set accordingly > Apply.

Note: Obviously this will kick you off, and you will need to change your IP address again to reconnect.

4. To change the password navigate to System > Password > change accordingly > Apply.

Find out your Cisco ASA version (Operating system and ASDM)

Posted on 17/11/2015 by Migrated

KB ID 0000690

Problem

With all the command changes that have come in in the past few versions, it seems when I get asked ‘how do you do xyz?” my first question is ‘What is the OS version on your ASA?’

So next time I get a blank look, I can just point them here.

Also see: ASA 5505 Determine Your License Version

Solution

Get your ASA version and ASDM version from the ASDM.

1. Connect to the ASA via ASDM.

2. Home > Device Dashboard > Device Information.

Get your ASA version and ASDM version from Command Line.

1. Connect to the ASA via CLI.

2. Execute the following command;

[box]show ver[/box]

Note: This is the shortened version of ‘show version‘.

To download new ASA software go here, (Note: Valid Cisco Warranty/SmartNet, and CCO account required to download software).

PeteNetLive

Technology that 'Just Works'

Tag Archives: locate

Cisco Catalyst Switches – Adding Licenses

Problem

Solution

Related Articles, References, Credits, or External Links

Windows – Getting Drivers for ‘Unknown Device’ or ‘Base System Device’

Problem

Solution

Drivers I’ve Had to Look For

Related Articles, References, Credits, or External Links

Exchange 2003 – NDR ‘This message is too large to send.’

Problem

Solution

Related Articles, References, Credits, or External Links

Windows – ‘The directory service has exhausted the pool of relative identifiers’

Problem

Solution

Related Articles, References, Credits, or External Links

Setup an HP 1800-24G (J9028B) Switch

Problem

Solution

Related Articles, References, Credits, or External Links

Find out your Cisco ASA version (Operating system and ASDM)

Problem

Solution

Get your ASA version and ASDM version from the ASDM.

Get your ASA version and ASDM version from Command Line.

Related Articles, References, Credits, or External Links