Power cable "CAB-ACE" can be used for cisco WS-C2960X-24PD-L. Same power cable is used for other Europian countries.
Tuesday 20 December 2016
Cisco power cable for Poland
Power cable "CAB-ACE" can be used for cisco WS-C2960X-24PD-L. Same power cable is used for other Europian countries.
Friday 16 December 2016
EoMPLS configuration Example
PC1:-
Configuration:-
PC1> show ip
NAME :
PC1[1]
IP/MASK :
10.1.1.10/24
GATEWAY :
255.255.255.0
DNS :
MAC :
00:50:79:66:68:00
LPORT : 10000
RHOST:PORT :
192.168.56.1:10001
MTU: : 1500
Verification:-
PC1> ping 10.1.1.2
84 bytes from 10.1.1.2 icmp_seq=1 ttl=255 time=20.748 ms
84 bytes from 10.1.1.2 icmp_seq=2 ttl=255 time=46.277 ms
84 bytes from 10.1.1.2 icmp_seq=3 ttl=255 time=47.200 ms
84 bytes from 10.1.1.2 icmp_seq=4 ttl=255 time=44.257 ms
84 bytes from 10.1.1.2 icmp_seq=5 ttl=255 time=34.722 ms
PC1> ping 10.1.1.3
84 bytes from 10.1.1.3 icmp_seq=1 ttl=255 time=69.798 ms
84 bytes from 10.1.1.3 icmp_seq=2 ttl=255 time=162.311 ms
84 bytes from 10.1.1.3 icmp_seq=3 ttl=255 time=100.966 ms
84 bytes from 10.1.1.3 icmp_seq=4 ttl=255 time=78.673 ms
84 bytes from 10.1.1.3 icmp_seq=5 ttl=255 time=90.670 ms
PC1> ping 10.1.1.11
84 bytes from 10.1.1.11 icmp_seq=1 ttl=64 time=43.250 ms
84 bytes from 10.1.1.11 icmp_seq=2 ttl=64 time=55.295 ms
84 bytes from 10.1.1.11 icmp_seq=3 ttl=64 time=58.007 ms
84 bytes from 10.1.1.11 icmp_seq=4 ttl=64 time=59.030 ms
84 bytes from 10.1.1.11 icmp_seq=5 ttl=64 time=51.903 ms
R1:-
Configuration:-
hostname R1
interface FastEthernet0/0
Description "Connected to PC1"
switchport access
vlan 100
spanning-tree
portfast
interface FastEthernet0/1
Description "Connected to R2"
switchport access
vlan 100
spanning-tree
portfast
interface Vlan100
ip address
10.1.1.2 255.255.255.0
R2:-
Configuration:-
ip vrf cust1
rd 1:1
route-target
export 1:1
route-target
import 1:1
interface Loopback0
ip address 2.2.2.2
255.255.255.255
interface FastEthernet0/1
Description "Connected to R1"
no ip address
xconnect 4.4.4.4
100 encapsulation mpls
interface FastEthernet2/0
Description "Connected to R3"
ip address
23.23.23.2 255.255.255.0
mpls ip
router ospf 10
log-adjacency-changes
network 2.2.2.2
0.0.0.0 area 0
network 23.23.23.2
0.0.0.0 area 0
router bgp 1
no synchronization
bgp log-neighbor-changes
neighbor 4.4.4.4
remote-as 1
neighbor 4.4.4.4
update-source Loopback0
no auto-summary
address-family
vpnv4
neighbor 4.4.4.4
activate
neighbor 4.4.4.4
send-community extended
exit-address-family
mpls ldp router-id Loopback0 force
Verfication:-
R2#sh bgp vpnv4 unicast all summary
BGP router identifier 2.2.2.2, local AS number 1
BGP table version is 1, main routing table version 1
Neighbor
V AS MsgRcvd MsgSent TblVer
InQ OutQ Up/Down State/PfxRcd
4.4.4.4
4 1 54
54 1 0
0 00:44:52 0
R2#show mpls forwarding-table
Local
Outgoing Prefix Bytes Label Outgoing
Next Hop
Label
Label or Tunnel Id Switched interface
16 Pop
Label 34.34.34.0/24 0 Fa2/0 23.23.23.3
17 18 4.4.4.4/32 0 Fa2/0 23.23.23.3
18 Pop
Label 3.3.3.3/32 0 Fa2/0 23.23.23.3
19 No
Label l2ckt(100) 19424 Fa0/1 point2point
R2#show mpls ip binding
2.2.2.2/32
in
label: imp-null
out
label: 19 lsr: 3.3.3.3:0
out
label: 16 lsr: 4.4.4.4:0
3.3.3.3/32
in
label: 18
out
label: imp-null lsr: 3.3.3.3:0 inuse
out
label: 18 lsr: 4.4.4.4:0
4.4.4.4/32
in
label: 17
out
label: 18 lsr: 3.3.3.3:0 inuse
out
label: imp-null lsr: 4.4.4.4:0
23.23.23.0/24
in
label: imp-null
out
label: imp-null lsr: 3.3.3.3:0
out
label: 17 lsr: 4.4.4.4:0
34.34.34.0/24
in
label: 16
out
label: imp-null lsr: 3.3.3.3:0 inuse
out
label: imp-null lsr: 4.4.4.4:0
R2#show mpls ldp neighbor
Peer LDP Ident:
3.3.3.3:0; Local LDP Ident 2.2.2.2:0
TCP
connection: 3.3.3.3.37189 - 2.2.2.2.646
State:
Oper; Msgs sent/rcvd: 70/71; Downstream
Up time:
00:54:39
LDP
discovery sources:
FastEthernet2/0, Src IP addr: 23.23.23.3
Addresses
bound to peer LDP Ident:
23.23.23.3 3.3.3.3 34.34.34.3
Peer LDP Ident:
4.4.4.4:0; Local LDP Ident 2.2.2.2:0
TCP
connection: 4.4.4.4.45408 - 2.2.2.2.646
State:
Oper; Msgs sent/rcvd: 63/61; Downstream
Up time:
00:46:34
LDP
discovery sources:
Targeted
Hello 2.2.2.2 -> 4.4.4.4, active, passive
Addresses
bound to peer LDP Ident:
34.34.34.4 4.4.4.4
R2#show mpls l2transport vc 100
Local intf
Local circuit Dest
address VC ID Status
-------------
-------------------------- --------------- ---------- ----------
Fa0/1
Ethernet
4.4.4.4 100
UP
R2#show mpls l2transport vc 100 detail
Local interface: Fa0/1 up, line protocol up, Ethernet up
Destination
address: 4.4.4.4, VC ID: 100, VC status: up
Output
interface: Fa2/0, imposed label stack {18 19}
Preferred path:
not configured
Default path:
active
Next hop:
23.23.23.3
Create time:
03:20:58, last status change time: 00:46:45
Signaling
protocol: LDP, peer 4.4.4.4:0 up
Targeted Hello:
2.2.2.2(LDP Id) -> 4.4.4.4, LDP is UP
Status TLV
support (local/remote) :
enabled/supported
LDP route
watch : enabled
Label/status
state machine : established,
LruRru
Last local
dataplane status rcvd: No fault
Last local
SSS circuit status rcvd: No fault
Last local
SSS circuit status sent: No fault
Last
local LDP TLV status sent: No fault
Last remote
LDP TLV status rcvd: No fault
Last remote
LDP ADJ status rcvd: No fault
MPLS VC labels:
local 19, remote 19
Group ID: local
0, remote 0
MTU: local
1500, remote 1500
Remote
interface description:
Sequencing:
receive disabled, send disabled
Control Word: On
(configured: autosense)
VC statistics:
transit packet
totals: receive 3766, send 8667
transit byte
totals: receive 275450, send 796027
transit packet
drops: receive 0, seq error 0, send 0
R3:-
Configuration:-
hostname R3
interface Loopback0
ip address 3.3.3.3
255.255.255.255
interface FastEthernet2/0
Description "Connected to R2"
ip address
23.23.23.3 255.255.255.0
mpls ip
interface FastEthernet2/1
Description "Connected to R4"
ip address
34.34.34.3 255.255.255.0
mpls ip
router ospf 10
log-adjacency-changes
network 3.3.3.3
0.0.0.0 area 0
network 23.23.23.3
0.0.0.0 area 0
network 34.34.34.3
0.0.0.0 area 0
mpls ldp router-id Loopback0 force
Verification:-
R3#show mpls ldp neighbor
Peer LDP Ident:
2.2.2.2:0; Local LDP Ident 3.3.3.3:0
TCP
connection: 2.2.2.2.646 - 3.3.3.3.37189
State:
Oper; Msgs sent/rcvd: 74/73; Downstream
Up time:
00:57:24
LDP
discovery sources:
FastEthernet2/0, Src IP addr: 23.23.23.2
Addresses
bound to peer LDP Ident:
2.2.2.2 23.23.23.2
Peer LDP Ident:
4.4.4.4:0; Local LDP Ident 3.3.3.3:0
TCP
connection: 4.4.4.4.49005 - 3.3.3.3.646
State:
Oper; Msgs sent/rcvd: 63/64; Downstream
Up time:
00:49:20
LDP
discovery sources:
FastEthernet2/1, Src IP addr: 34.34.34.4
Addresses
bound to peer LDP Ident:
34.34.34.4 4.4.4.4
R3#show mpls forwarding-table
Local
Outgoing Prefix Bytes Label Outgoing
Next Hop
Label
Label or Tunnel Id Switched interface
18 Pop
Label 4.4.4.4/32 180845 Fa2/1 34.34.34.4
19 Pop
Label 2.2.2.2/32 89623 Fa2/0 23.23.23.2
R3#show mpls ip binding
2.2.2.2/32
in
label: 19
out
label: imp-null lsr: 2.2.2.2:0 inuse
out
label: 16 lsr: 4.4.4.4:0
3.3.3.3/32
in
label: imp-null
out
label: 18 lsr: 2.2.2.2:0
out
label: 18 lsr: 4.4.4.4:0
4.4.4.4/32
in
label: 18
out
label: 17 lsr: 2.2.2.2:0
out
label: imp-null lsr: 4.4.4.4:0 inuse
23.23.23.0/24
in label: imp-null
out
label: imp-null lsr: 2.2.2.2:0
out
label: 17 lsr: 4.4.4.4:0
34.34.34.0/24
in
label: imp-null
out
label: 16 lsr: 2.2.2.2:0
out
label: imp-null lsr: 4.4.4.4:0
R3#sh ip ospf neighbor
Neighbor ID
Pri State Dead Time Address Interface
4.4.4.4
1 FULL/DR 00:00:36 34.34.34.4 FastEthernet2/1
2.2.2.2
1 FULL/DR 00:00:32
23.23.23.2 FastEthernet2/0
R3#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M -
mobile, B - BGP
D - EIGRP,
EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF
NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF
external type 1, E2 - OSPF external type 2
i - IS-IS,
su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS
inter area, * - candidate default, U - per-user static route
o - ODR, P -
periodic downloaded static route, H - NHRP
+ -
replicated route, % - next hop override
Gateway of last resort is not set
2.0.0.0/32 is
subnetted, 1 subnets
O 2.2.2.2
[110/2] via 23.23.23.2, 00:54:20, FastEthernet2/0
3.0.0.0/32 is
subnetted, 1 subnets
C 3.3.3.3 is
directly connected, Loopback0
4.0.0.0/32 is
subnetted, 1 subnets
O 4.4.4.4
[110/2] via 34.34.34.4, 00:51:06, FastEthernet2/1
23.0.0.0/8 is
variably subnetted, 2 subnets, 2 masks
C
23.23.23.0/24 is directly connected, FastEthernet2/0
L
23.23.23.3/32 is directly connected, FastEthernet2/0
34.0.0.0/8 is
variably subnetted, 2 subnets, 2 masks
C
34.34.34.0/24 is directly connected, FastEthernet2/1
L 34.34.34.3/32 is directly connected,
FastEthernet2/1
R4:-
Configuration:-
ip vrf cust1
rd 1:1
route-target
export 1:1
route-target
import 1:1
interface Loopback0
ip address 4.4.4.4
255.255.255.255
interface FastEthernet0/1
Description "Connected to R5"
no ip address
xconnect 2.2.2.2 100 encapsulation mpls
interface FastEthernet2/1
Description "Connected to R3"
ip address
34.34.34.4 255.255.255.0
speed auto
duplex auto
mpls ip
router ospf 10
log-adjacency-changes
network 4.4.4.4
0.0.0.0 area 0
network 34.34.34.4
0.0.0.0 area 0
router bgp 1
no synchronization
bgp
log-neighbor-changes
neighbor 2.2.2.2
remote-as 1
neighbor 2.2.2.2
update-source Loopback0
no auto-summary
address-family
vpnv4
neighbor 2.2.2.2
activate
neighbor 2.2.2.2
send-community extended
exit-address-family
mpls ldp router-id Loopback0 force
R5:-
Configuration:-
interface
FastEthernet0/0
Description "Connected to PC2"
switchport access vlan 100
interface
FastEthernet0/1
Description "Connected to R4"
switchport access vlan 100
interface
Vlan100
ip address 10.1.1.3 255.255.255.0
Verification:-
R5# ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max
= 92/126/208 ms
R5#ping 10.1.1.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.10, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max
= 92/119/180 ms
R5#show spanning-tree vlan 100 summary
Root bridge for VLAN100 is 32768.cc01.0ec0.0000.
PortFast BPDU Guard is disabled
UplinkFast is disabled
BackboneFast is disabled
Name
Blocking Listening Learning Forwarding STP Active
-------------------- -------- --------- --------
---------- ----------
VLAN100
0 0 0 2 2
R5#show spanning-tree vlan 100 brief
VLAN100
Spanning tree
enabled protocol ieee
Root ID Priority
32768
Address cc01.0ec0.0000
Cost 19
Port 2 (FastEthernet0/1)
Hello
Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority
32768
Address cc05.1c8c.0001
Hello
Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging
Time 300
Interface Designated
Name
Port ID Prio Cost Sts Cost Bridge ID Port ID
-------------------- ------- ---- ----- --- -----
-------------------- -------
FastEthernet0/0
128.1 128 19 FWD
19 32768 cc05.1c8c.0001 128.1
FastEthernet0/1
128.2 128 19 FWD
0 32768 cc01.0ec0.0000 128.2
PC2:-
Configuration:-
PC2> show ip
NAME :
PC2[1]
IP/MASK :
10.1.1.11/24
GATEWAY :
255.255.255.0
DNS :
MAC :
00:50:79:66:68:01
LPORT : 10010
RHOST:PORT :
192.168.56.1:10011
MTU: : 1500
Verification:-
PC2> ping 10.1.1.3
84 bytes from 10.1.1.3 icmp_seq=1 ttl=255 time=44.685 ms
84 bytes from 10.1.1.3 icmp_seq=2 ttl=255 time=39.397 ms
84 bytes from 10.1.1.3 icmp_seq=3 ttl=255 time=30.531 ms
84 bytes from 10.1.1.3 icmp_seq=4 ttl=255 time=29.676 ms
84 bytes from 10.1.1.3 icmp_seq=5 ttl=255 time=29.988 ms
PC2> ping 10.1.1.2
84 bytes from 10.1.1.2 icmp_seq=1 ttl=255 time=88.275 ms
84 bytes from 10.1.1.2 icmp_seq=2 ttl=255 time=83.330 ms
84 bytes from 10.1.1.2 icmp_seq=3 ttl=255 time=105.148 ms
84 bytes from 10.1.1.2 icmp_seq=4 ttl=255 time=73.325 ms
84 bytes from 10.1.1.2 icmp_seq=5 ttl=255 time=61.766 ms
PC2> ping 10.1.1.10
84 bytes from 10.1.1.10 icmp_seq=1 ttl=64 time=40.029 ms
84 bytes from 10.1.1.10 icmp_seq=2 ttl=64 time=82.339 ms
84 bytes from 10.1.1.10 icmp_seq=3 ttl=64 time=50.745 ms
84 bytes from 10.1.1.10 icmp_seq=4 ttl=64 time=40.292 ms
84 bytes from 10.1.1.10 icmp_seq=5 ttl=64 time=61.310 ms
For More Blogs:- Please visit www.Hevitech.com
For More Blogs:- Please visit www.Hevitech.com
Tuesday 27 September 2016
Tuesday 20 September 2016
%ADJ-5-RESOLVE_REQ_FAIL: Adj resolve request failed for
Today I faced an issue where lots of logs " %ADJ-5-RESOLVE_REQ_FAIL: Adj resolve request failed for " are generated on cisco 3750 switch.
It will not impact anything but logs keeps filling the buffer due to which some important logs can be overwritten.
This is due to bug "CSCug43307" in the IOS.
As an workaround use below command to stop these logs.
" no ip cef optimize neighbor resolution "
Sunday 14 August 2016
Difference between POE, POE+ and UPOE
Below is the quick summary of the differences between POE,POE+ and UPOE.
POE is the oldest standard for the devices which can be powered on from the switch. POE enabled switches can only provide upto 15W to the connected devices like phones.
Later on POE+ standard was evolved. Switches which are complied to POE+ standard can provide 30W of power to the connected devices.
Latest standard in this series is UPOE which is not a universal standard but a cisco Proprietary. According to which UPOE enabled switches can provide 60 W of power to the connected devices. Now we can power up not only phones but also PCs/Laptops from the switches.
Below are few more differences.
Thursday 4 August 2016
RJ45 to RJ45 Console Cable
I
saw there is RJ45 to RJ45 console cable is available on Cisco site. It has RJ45 connector at both the ends.
It looks like this:-
But How can we use it?
Can we connect it to our laptop's ethernet port?
Then,
after lot of research I came to know that we cannot use this cable direct with
laptop.
We
have to have a RJ45 to DB9 connector (if DB9 is available on the machine) and
another adaptor DB9 to USB incase DB9 is not available in your machine.
RJ45 to RJ45 cable is used for access server with RJ45 ports
like Digiport server or Blackbox console device to Cisco device connectivity.
The
pinouts for RJ45 to RJ45 console cable is given below:-
Monday 1 August 2016
Cisco EOL SFP's and its replacement
Cisco has announced EOL notification for many SFPs. Below are the few common Cisco SFPs and their replacement.
Baby Gaint Frame Vs Jumbo Frame...
Frames which are up to 1600 Bytes are called as Baby Gaint.
Ethernet frames from 1600 to 9216 Bytes are known as Jumbo frames.
Ethernet frames from 1600 to 9216 Bytes are known as Jumbo frames.
Subscribe to:
Posts (Atom)