Friday, September 26, 2014

SSH to other device from cisco device if you want different username

SSH to other device from Cisco device if you want different username

 

ROUTER#ssh -l admin 4.2.2.2

Password:

Type help or '?' for a list of available commands.

FIREWALL> en




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Thursday, September 25, 2014

ACS TACACS username and password

1.       How to create username and password in ACS TACACS server

 

username user password plain cisco123 role admin

 

2.       Repository [ FTP ]

 

repository NAME

  url ftp://XX.XX.XX.XX/

  user cisco password plain cisco123




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Tuesday, September 23, 2014

Sprint shape

 

called NETWORK SERVICES 203-564-8150

- spoke to Ameer Ali

- update him on my findings, i believe the problem may be resolved now

- i added a 10Mbps shaping policy to the geneva-switzerland-mpls QoS config

  and applied it to gig0/0 WAN

- since doing so, the packet loss on ToS 184 (classA) has cleared.

- zero packet loss between pe/ce and stamford to geneva CE.

- seeing default-class drops only in CE due to exceeding 10Mbps shaper

- no drops in ClassA

- this shaping policy was not present before so the Geneva router thought the

  circuit was 100Mbps, so this is why the LEC Colt was dropping packets at

  layer 2 due to their 10Mbps policing. Layer 2 transport treats all packets

  the same since it does not look at QoS markings, so this explains why

  voice was affected even though CE/PE had QoS configured.

- they will monitor for further voice issues and I we will do the same

- he asked i send him an emailing detailing what changes were made.

 

 

policy-map ipcos-Q1C1-parent

class class-default

  shape average 10000000

   service-policy ipcos-Q1C1

 




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Friday, September 19, 2014

nslookup for dns

 

How to Use Nslookup to Verify DNS Configuration

 

C:\> nslookup

Default Server: pdc.corp.example.com

Address: 192.168.6.13

> server 10.255.255.255

Default Server: dns1.example.com

Address: 10.255.255.255

> set q=mx

> contoso.com.

Server: dns1.example.com

Address: 192.168.10.10

contoso.com MX preference = 10, mail exchanger = mail1.contoso.com

contoso.com MX preference = 10, mail exchanger = mail2.contoso.com

 




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Barracuda clustering

 

Barracuda Clustering

 

ADVANCED -> Linked Management

 

1.       Clustered shared Secret password should be same on both Barracuda’s

2.       192.168.200.200 [ master ] ->  set 192.168.200.200 ACTIVE

3.       192.168.200.202 [ Slave ] -> set 192.168.200.202  STANDBY

4.       192.168.200. 202[Slave device]->  set 192.168.200.200 as ACTIVE

 

 




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Tuesday, September 16, 2014

Enabling syslog logging



Many network administrators overlook the importance of router logs. Logging can use for fault notification, network forensics, and security auditing.

Cisco routers log messages can handle in five different ways:

Console logging:By default, the router sends all log messages to its console port. Hence only the users that are physically connected to the router console port can view these messages.

Terminal logging:It is similar to console logging, but it displays log messages to the router's VTY lines instead. This is not enabled by default   
Buffered logging:This type of logging uses router's RAM for storing log messages. buffer has a fixed size to ensure that the log will not deplete valuable system memory. The router accomplishes this by deleting old messages from the buffer as new messages are added.

Syslog Server logging :The router can use syslog to forward log messages to external syslog servers for storage. This type of logging is not enabled by default.

SNMP trap logging:The router is able to use SNMP traps to send log messages to an external SNMP server.


Sample router log messages:


Level

Level name

Router messages

0

Emergencies

System shutting down due to missing fan tray

1

Alerts

Temperature limit exceeded

2

Critical

Memory allocation failures

3

Errors

Interface Up/Down messages

4

Warnings

Configuration file written to server, via SNMP request

5

Notifications

Line protocol Up/Down

6

Information

Access-list violation logging

7

Debugging

Debug messages

Configuration Overview:

A)Console logging:

The router does not check if a user is logged into the console port or a device is attached to it; if console logging is enabled, messages are always sent to the console port that can cause CPU load.

To stop the console logging, use the "no logging console" global configuration command .you might want to limit the amount of messages sent to the console with the "logging console level" configuration command (for example, logging console Informational).


B) Buffered logging:

You want your router to record log messages, instead of just displaying them on the console.To use logging buffered configuration command to enable the local storage of router log messages:

Router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#logging buffered informational
Router(config)

Enable dhcp client on CISCO ASA firewall


If you want to receive IP address from DHCP server , Please use following configuration.

 

interface Vlan2

 nameif outside

 security-level 0

 ip address dhcp setroute


Enable dhcp client on CISCO ASA firewall

If you want to receive IP address from DHCP server , Please use following configuration.

 

interface Vlan2

 nameif outside

 security-level 0

 ip address dhcp setroute




Please consider the environment before printing this e-mail

Disclaimer: This  communication  is  for the exclusive use of the intended recipient(s) and  shall  not attach any liability on the originator or ITC Infotech India Ltd./its  Holding company/ its Subsidiaries/ its Group Companies. If you are the addressee, the contents of this e-mail are intended for your use only and it shall  not be forwarded to any third party, without first obtaining written authorization from the originator or ITC Infotech India Ltd./ its Holding company/its  Subsidiaries/ its Group Companies. It may contain information which is confidential and legally privileged and the same shall not be used or dealt with  by any  third  party  in  any manner whatsoever without the specific consent  of  ITC  Infotech India Ltd./ its Holding company/ its Subsidiaries/ its Group Companies.

Enabling syslog logging on Cisco Switches and routers

no logging console
logging buffered 64000
logging monitor informational
logging buffered informational
logging trap errors
logging source-interface xxxx
logging 10.20.207.105


Sunday, September 14, 2014

Cisco ASA failover

Primary Firewall ---------------- failover
failover lan unit primary
failover lan interface failover Management0/0
 failover link failover Management0/0
failover interface ip failover 192.168.254.1 255.255.255.0 standby 192.168.254.2

Secondary Firewall ------------------ config t
no failover failover lan unit secondary
failover lan interface failover Management0/0 failover link failover Management0/0
 failover interface ip failover 192.168.254.1 255.255.255.0 standby 192.168.254.2 failover ------
sh failover
sh run failover
sh failover interface

Etherchennal - Find port where traffic goes

How to find the traffic pass through Etherchennal ? -------------------------------------------------------------------------------------------- STM-ACCESS-07A03-SW01#remote login switch STM-ACCESS-07A03-SW01-sp#test etherchannel load-balance interface po 42 ip 10.20.22.148 10.20.209.101 -------------------------------------------------------------------------------------------------------