HP Procurve – CLI Common Troubleshooting Commands

Common CLI commands used for troubleshooting

 

— Ping ——-
Ping <x.x.x.x>
—————

— Trace Route —–
Traceroute <x.x.x.x>
————————-

— Show IP Addresses ——-
Show IP
——————————

— Show VLAN’s ——
Show vlan
————————-

— Show IP Routes —–
Show ip route
—————————–

Posted in HP Procurve Switch | Leave a comment

HP Procurve – CLI Change VLAN IP Address

​CLI to change the IP Address of a VLAN

— Command ————

switch # config t
(config) # show vlans
(config) # vlan <ID of VLAN>
(vlan-ID )# ip address <IP ADDRESS OF VLAN><NET MASK>
(vlan-ID) # exit switch
(config )# exit
write mem

————————

Posted in HP Procurve Switch | Leave a comment

HP Procurve – CLI Enable Jumbo Frames

CLI to enable jumbo frames for a VLAN

— Command ——————

switch # config t switch
(config) # show vlans switch
(config) # vlan <ID of VLAN> jumbo switch
(config )# exit switch # write mem

——————————

Posted in HP Procurve Switch | Leave a comment

HP Procurve Switch – Flush all non-permanent entries in the ARP cache

​Flush all non-permanent entries in the ARP cache.

— Command —————
clear arp
——————————-

Posted in HP Procurve Switch | Leave a comment

HP Procurve – CLI Configure IP Helper Address

Configure a IP Helper Address for a HP Procurve Switch

— Command —————-
enable config t vlan
<VLAN ID> ip helper-address <IP ADDRESS of DHCP SERVER>
exit write mem
——————————–

Show ip helper-addresses on system

— Command —————-
show ip helper-address
——————————–

Posted in HP Procurve Switch | Leave a comment

HP Procurve 5400 – Configuring sFlow

Configuring sFlow The following sFlow commands allow you to configure sFlow instances via the CLI.

 

— Command ————————————
[no] sflow <receiver-instance> destination <ip-address> [udp-port-num]
————————————————–

Enables an sFlow receiver/destination. The receiver-instance number must be a 1, 2, or 3. By default, the udp destination port number is 6343.

To disable an sFlow receiver/destination, enter no sflow <receiver-instance>.

— Command ———————————-
sflow <receiver-instance> sampling <port-list> <sampling rate>
————————————————–

Once an sFlow receiver/destination has been enabled, this command enables flow sampling for that instance. The receiver-instance number is 1, 2, or 3, and the sampling rate is the allowable non-zero skipcount for the specified port or ports. To disable flow-sampling for the specified port-list, repeat the above command with a sampling rate of “0”.

— Command ————————————-
sflow <receiver-instance> polling <port-list> <polling interval>
—————————————————–

Once an sFlow receiver/destination has been enabled, this command enables counter polling for that instance. The receiver-instance number is 1, 2, or 3, and the polling interval may be set to an allowable non-zero value to enable polling on the specified port or ports.

 

Example:
— Command————————–

(config)# sflow 1 destination 10.1.2.5 6343
(config)# sflow 1 sampling ethernet A1-A24 128
(config)# sflow 1 polling ethernet A1-A24 30
——————————————–

 

To View counter-polling
Viewing sFlow Configuration and Status The following sFlow commands allow you to display sFlow configuration and status via the CLI.

— Command ————————————–
show sflow agent
—————————————————–
Displays sFlow agent information. The agent address is normally the ip address of the first vlan configured.

— Command —————————————
show sflow <receiver instance> destination
——————————————————-

Displays information about the management station to which the sFlow samplingpolling data is sent.

— Command —————————————–
show sflow <receiver instance> sampling-polling <port-list/range>
——————————————————–
Displays status information about sFlow sampling and polling.

 

To Remove counter-polling

Remove sflow Polling from a Port

— Command ———————–
sflow 1 polling <Port Number> 0
————————————–

Remove sflow Sampling from a Port

— Command————————-
sflow 1 sampling <Port Number> 0
——————————————

 

Posted in HP Procurve Switch | Leave a comment

MS Exchange – Event ID 2017 MSMQ Message Queuing Service cannot start

Event ID 2078 Source MSMQ

The Message Queuing service cannot start. The checkpoint files cannot be recovered. To start the Message Queuing service without losing consistency, you must correct or recover corrupted checkpoint and log files. To start the service for emergency use (with a potential loss of data consistency), delete the files QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, and MQInSeqs.lg2 from the Msmq\Storage folder and add the DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\LogDataCreated with a value of 0. Error 0x80070020: The process cannot access the file because it is being used by another process.

Applies to: Microsoft Exchange Microsoft Windows Server

Solution: — Delete checkpoint files

To delete checkpoint files:

1.Open Windows Explorer and browse to your storage direcotry. This is typically located under C:\Windows\System32\msmq\storage. 2.Delete the following files: MQInSeqs.lg1, MQInSeqs.lg2, MQTrans.lg1, MQTrans.lg2, QMLog file. 3.Open Registry Editor. To open Registry Editor, click Start. In the search box, type regedit, and then press ENTER. 4.Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters. 5.Click Parameters. 6.On the Edit menu, point to New, and then click DWORD (32-bit) Value. 7.In Name, type LogDataCreated, and ensure that the value is set to 0. 8.Close Registry Editor.

 

— Restart the MSMQ Service

To restart the MSMQ Service: 1.Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER. 2.Right-click Message Queuing, and then click Restart. You must restart all the dependent services, as well.

More Information: http://technet.microsoft.com/en-us/library/cc773632(v=ws.10).aspx

 

Posted in Microsoft Exchange | Leave a comment

How to test SMTP operations using Telnet

How to test SMTP operations using Telnet

1. Telnet into Exchange server service using TCP port 25.

— Command ———
telnet mail.mailserver.com 25
———————

2. Issue the following smtp command sequence

— Command ——–
helo mailserver.com <enter>
——————–
response should be as follows  250 OK

— Command ——-
mail from: <your Email Address><enter>
——————-
response should be as follows  250 OK – mail from <your Email address>

— Command ——-
rcpt to: <recipient address><enter>
——————–
response should be as follows  250 OK – Recipient <recipient address>

— Command ——–
data<enter>
——————–
response should be as follows  354 Send data.  End with CRLF.CRLF

— Command ——-
To: <recipient’s display name><enter>
From: <your display name><enter>
Subject: <Subject field of Email message><enter>
<Enter you body text><enter><enter> . <enter>
——————–
response should be as follows  250 OK

— Command ——–
quit<enter>
——————-

Posted in Microsoft Exchange | Leave a comment

Microsoft Exchange – Reverse DNS does not match SMTP Banner

Error: Warning – Reverse DNS does not match SMTP Banner

The Cisco PIX firewall device uses an SMTP protocol filtering feature that is named Mailguard. When the Mailguard feature is turned on, it blocks all Extended Simple Mail Transfer Protocol (ESMTP) commands.

————————————————

220 ************************* [640 ms] EHLO please-read-policy.mxtoolbox.com 250-mail.domainxx.com Hello [64.20.227.133]

————————————————-

Should show

————————————————–

220 Mail.dominxx.com[640 ms] EHLO please-read-policy.mxtoolbox.com 250-mail.domainxx.com Hello [64.20.227.133]

—————————————————-

 

Solution

Turn off mailguard on the CIsco ASA Firewall

— Command ————————————-

no fixup protocol smtp 25

—————————————————

Posted in Microsoft Exchange | Leave a comment

Default Settings for Exchange Virtual Directories

TechNet Article on Default Exchange Server Virtual Directory Settings

Exchange Server 2013 automatically configures multiple Internet Information Services (IIS) virtual directories during installation. This topic contains information about the default IIS authentication settings and default Secure Sockets Layer (SSL) settings for the Client Access and Mailbox servers.

http://technet.microsoft.com/en-us/library/gg247612.aspx

Posted in Microsoft Exchange | Leave a comment