- Details
-
Category: Networking
-
Created on Wednesday, 03 February 2016 21:02
-
Written by Tomasz Zdunek
This is update to my previous article: VLAN translaction on Alcatel but configuration created for OmniSwitch 6900.
VLAN 4050 - The VLAN that exists on the translating switch, to prevent VLAN overlapping it will be translated to VLAN900.
LINKAGG 100 - The uplink to other switch that has VLAN4050 configured but for other dedicated service. Due VLANs overlapping translaction is required.
PORT 1/9 & PORT 1/7 - Trunks ports to a server or other VLAN aware device (switch/router). Frames are represented as tagged frames with VLAN 900.
- Details
-
Category: Networking
-
Created on Wednesday, 03 February 2016 19:55
-
Written by Tomasz Zdunek
I have found tricky to configure SSH on HP switches integrated in HP BladeSystem C7000 chassis.
The manuals doesnt cover are requiremnts steps so here you will find the way how to configure the SSH/CONSOLE/AUX lines.
Read more: HP 6125XLG Line (SSH/AUX etc.) authentication
- Details
-
Category: Cisco
-
Created on Wednesday, 15 October 2014 19:42
-
Written by Tomasz Zdunek
There are alot of articles covering subject of IOU running on Linux and Unix. I would like to go deeper and specific how we can create some useful confiugration on NETBSD/SPARC to have this maybe easier in some cases.
The goals I've set are:
-
Ony one IOU instance per NETBSD appliance
-
Use GNS3 clouds (UDP TAP) to provide connectivity between each NETBSD instance and other part of networks. This was really forced, in first instance I tried to create some kind of bridge, but NETBSD didn't recognize second LE (ethernet card) correctly
-
Make it as more automaticated as it is possible
-
Keeps each service separated
Read more: Configuring netbsd (sparc) appliance for IOU
- Details
-
Category: Cisco
-
Created on Tuesday, 02 December 2014 14:42
-
Written by Tomasz Zdunek
You can be put in situation to connect two or more L3 devices using L3VPN. The configuration isn't complex, and will work unless the path between devices invloves the non-MPLS enabled switches. If you connect ASR routers using other devices in the network it can be tricky. BGP sessions is not an issue, but MPLS tags. For L3VPN two labels are required:
-
Outer Label - specifices outgoing interface to reach L3VPN enabled neighbor.
-
Inner Label - provides information about VRF instance for the neighbor
The issue I got was lack of Outer Label because the path toward L3VPN neighor was not MPLS-enabled. It was simply 802.1Q subinterface, on top of bundle-interface. The sessions have been established, but no traffic was seen on opposite site.
Read more: L3VPN on Cisco XR - without MPLS enabled switches