Hi,
We have a SAN vlan (46) and a Data vlan (45) – on a single Cisco switch. To do inter-site data replication I need to make the trunk'd SAN connections aware of the VLAN's.
Reading the NetApp docs I've done the following –
kdcsan2> ifconfig multitrunk1 down
kdcsan2> vlan create multitrunk1 45 46
kdcsan2> ifconfig multitrunk1-45 10.1.45.8 netmask 255.255.255.0 kdcsan2> ifconfig multitrunk1-46 10.1.46.2 netmask 255.255.255.0
kdcsan2> ifconfig multitrunk1-45 up kdcsan2> ifconfig multitrunk1-46 up
But I haven't been able to to ping the box via either IP address. The switch ports are configured for the 46 vlan so at the very least I should be able to ping the switch gateway.
The multitrunk1 consists of two nics in a fas270 going into two Cisco switch ports.
Any clues as to what I'm doing wrong ? Do I need to define multiple gateways ?
Thanks in advance, Raj.
On 9/4/07, Raj Patel phigmov@gmail.com wrote:
Hi,
We have a SAN vlan (46) and a Data vlan (45) – on a single Cisco switch. To do inter-site data replication I need to make the trunk'd SAN connections aware of the VLAN's.
---8<---
But I haven't been able to to ping the box via either IP address. The
switch ports are configured for the 46 vlan so at the very least I should be able to ping the switch gateway.
The multitrunk1 consists of two nics in a fas270 going into two Cisco switch ports.
Any clues as to what I'm doing wrong ? Do I need to define multiple gateways ?
Make sure you have the switch configured to do VLAN trunking (dot1q) as well, and define the VLANs on the trunk in the switch.
Hi,
I managed to sort this out -
The Cisco guys had to configure the ports for each nic to trunk -
Switchport trunk encapsulation dot1q Switchport mode trunk Media type rj45
Whats the simplest way to write the new vlan configs to file ? Do I just add them into /etc/rc or if I go into the web interface and re-apply the settings will these write the files ?
Cheers, Raj.
The vlan configs need to go int /etc/rc. They are not persistent otherwise.
#Regenerated by registry Mon Jul 30 08:44:13 EDT 2007 #Auto-generated by setup Tue Jun 26 17:09:34 EDT 2007 hostname xxxx ifconfig e0a mediatype auto ifconfig e0b mediatype auto ifconfig e0c mediatype auto ifconfig e0d mediatype auto vif create multi aaa-trunk e0a e0b vif create multi bbb-trunk e0d e0c vlan create aaa-trunk 990 988 999 vlan create bbb-trunk 804 809 ifconfig bbb-tru-804 x.x.x.x netmask 255.255.255.0 ifconfig bbb-tru-809 x.x.x.x netmask 255.255.255.0 ifconfig aaa-trunk-999 x.x.x.x netmask 255.255.252.0 route add default x.x.x.x routed on options dns.domainname x.x.x.x options dns.enable on options nis.enable on savecore
Eric Silberberg Infrastructure Systems Services NC State University 2620 Hillsborough Raleigh, NC 27695 919-513-1175
Cheers Eric - between your advice and Darren Soothills I managed to sort this out.
The sticking point was removing an ifconfig I had in place for the multitrunk kicking in before the ifconfigs for the vlan interfaces.
As an aside it would be super useful if there was a repository of annotated DataOnTap /etc/rc files available as a reference somewhere . . . .
Raj.
On 9/7/07, Eric Silberberg edsilber@gw.fis.ncsu.edu wrote:
The vlan configs need to go int /etc/rc. They are not persistent otherwise.
#Regenerated by registry Mon Jul 30 08:44:13 EDT 2007 #Auto-generated by setup Tue Jun 26 17:09:34 EDT 2007 hostname xxxx ifconfig e0a mediatype auto ifconfig e0b mediatype auto ifconfig e0c mediatype auto ifconfig e0d mediatype auto vif create multi aaa-trunk e0a e0b vif create multi bbb-trunk e0d e0c vlan create aaa-trunk 990 988 999 vlan create bbb-trunk 804 809 ifconfig bbb-tru-804 x.x.x.x netmask 255.255.255.0 ifconfig bbb-tru-809 x.x.x.x netmask 255.255.255.0 ifconfig aaa-trunk-999 x.x.x.x netmask 255.255.252.0 route add default x.x.x.x routed on options dns.domainname x.x.x.x options dns.enable on options nis.enable on savecore
Eric Silberberg Infrastructure Systems Services NC State University 2620 Hillsborough Raleigh, NC 27695 919-513-1175
-
Eric Silberberg -
Nils Vogels -
Raj Patel